Microsoft.CloudShell Namespace Registration issue in Azure Cloud Shell

[weeyin83]

Describe the bug

Azure Cloud Shell shows this message on every login:

Storage fileshare subscription subscription ID is not registered to Microsoft.CloudShell Namespace. Please follow these instructions "https://aka.ms/RegisterCloudShell" to register. In future, unregistered subscriptions will have restricted access to CloudShell service.

Related command

No related command, this happens when the Azure Cloud Shell is started up

Errors

Storage fileshare subscription is not registered to Microsoft.CloudShell Namespace. Please follow these instructions "https://aka.ms/RegisterCloudShell" to register. In future, unregistered subscriptions will have restricted access to CloudShell service.

Issue script & Debug output

n/a

Expected behavior

The Cloud Shell should not be displaying a 'not registered' message while the Microsoft.CloudShell Namespace is clearly registered.

Environment Summary

Azure Cloud Shell environment from the Azure portal

Additional context

This is the same as #27699 that is supposed to be resolved.

[azure-client-tools-bot-prd]

Hi @weeyin83
Find similar issue #27699.

Issue title	Microsoft.CloudShell Namespace Registration issue in Azure Cloud Shell - Started This Afternoon for No Reason.
Create time	2023-10-27
Comment number	0

---

Please confirm if this resolves your issue.

[yonzhan]

Thank you for opening this issue, we will look into it.

[microsoft-github-policy-service]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @maertendMSFT.

[jsntcy]

@hima-gadupudi, could you please help take a look?

[smereczynski]

Same here on fresh Azure Plan Subscription.

[mikepowell]

This may not be a common scenario, but in case it's helpful I had this issue when connecting to a storage account that had been recently moved from a subscription that did not have Microsoft.CloudShell registered, to one that did have it registered. Re-registering the provider on the subscription didn't help, but deleting the fileshare and unmounting/recreating it did make the warning go away.

[mbifeld]

From #27689 , resetting user settings fixes the issue. We'll look into adjusting the warning messages to tell users to reset user settings after registering. Closing issue, please reopen if resetting user settings doesn't fix it.