How to re-enable development access on my existing legacy tenant.

Ah T 0 Reputation points
2025-12-24T10:16:49.18+00:00

I am unable to enable application development on my Azure Sphere device.

The device previously created an Azure Sphere tenant ("WD") and now the tenant is in LegacyAccessState = Paused.

Error received:

LegacyAccessDenied – Access paused due to tenant legacy access restrictions (403)

Because an Azure Sphere device can only be used once to create a tenant, I cannot create a new tenant.

I request Microsoft to re-enable development access or migrate this legacy tenant so that I can continue application development using SDK 25.04.

I can give you the Tenant ID by your request.

Azure Sphere
Azure Sphere

An Azure internet of things security solution including hardware, operating system, and cloud components.

0 comments

2 answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2025-12-24T10:16:57.75+00:00

    To re-enable development access on your existing Azure Sphere legacy tenant, you will need to use the Azure Sphere CLI to enable access. Since your tenant is currently in a paused state, you can follow these steps:

    1. Open a command-line interface (PowerShell, Windows Command Prompt, or Linux command shell) with administrator privileges.
    2. Log in to Azure if you haven't done so already: 
         az login
    3. Re-enable access to your legacy tenant by using the following command: 
         az sphere tenant enable-access --tenant-id <YourTenantId>
      Replace <YourTenantId> with your actual tenant ID.

    After executing this command, users with Legacy user roles for the tenant should be able to perform tenant operations again. However, it is recommended to pause access for security reasons unless you are still using Legacy while migrating to Integrated.

    If you encounter any issues or errors, please refer to the Azure Sphere documentation for troubleshooting guidance.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Anonymous
    2025-12-24T23:14:37.04+00:00

    HIi Ah T

    The error message you’re seeing indicates that the tenant access is paused due to legacy access restrictions, and since that tenant is in a paused state, you can’t create a new one with the same device.

    Here’s what you might try to resolve the issue:

    1. Check the Azure Sphere Documentation: It seems there’s documentation regarding legacy tenants and their management, so make sure you’re familiar with the migration process if that’s applicable. You may need to migrate from the legacy tenant to an integrated setup. Here's a helpful link to get you started: Migrate from Azure Sphere (Legacy) to Azure Sphere (Integrated).
    2. Contact Support: As your tenant is in LegacyAccessState = Paused, you will likely need to contact Microsoft support for assistance with re-enabling development access. They may have specific steps that can reactivate your access or migrate your tenant correctly.
    3. Consider Permissions: Ensure that you have the correct admin permissions necessary to manage the Azure Sphere tenant. This oversight may also lead to access problems.
    4. Attempt CLI Commands: If you have access to the Azure CLI, you might try running commands to enable development on your device again, if applicable. The command to enable development generally looks like this: 
         az sphere device enable-development --resource-group MyResourceGroup --catalog MyCatalog --device <DeviceIdValue>
    5. Use the Azure Portal: You can also use the Azure Portal to check your current device's state and see if any changes can be applied directly through the UI.

    References

    I Hope this helps. Do let me know if you have any further queries.

    Thank you!

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.