Azure Sphere claim to a tenant in expired Active Directory Trial

AshokPeddakotla-MSFT 30,076 Reputation points

My azure sphere devt kit was claimed to a tenant under the trial azure active directory account. As i didnt manage to upgrade the account, the subscription data was deleted.

  Now i have problem using the azure sphere devt kit. Anyway to reset/unlink the tenant at the azure backend?

warn: You don't have access to any Azure Sphere tenants.

error: Failed to create an Azure Sphere tenant with your device, this may be because it was already claimed to a different Azure Sphere tenant.

[Note: As we migrate from MSDN, this question has been posted by an Azure Cloud Engineer as a frequently asked question.]

Source: MSDN

Azure Sphere
Azure Sphere
An Azure internet of things security solution including hardware, operating system, and cloud components.
163 questions
0 comments No comments
{count} vote

Accepted answer
  1. António Sérgio Azevedo 7,666 Reputation points Microsoft Employee

    Please confirm when did you claim the device? Was it before or after 19.10 SDK version?

    See: "Migrate an individual"

    If you claimed it before 19.10, can you try the following:

    To migrate a tenant:

    azsphere tenant migrate  

    If you are prompted, log in again using your old Azure Sphere login—that is, the work or school account you used with the 19.09 (or earlier) release. After this login, you will see information about your old environment. The user identity that the command output shows might be different from the identity with which you logged in to the new environment.

    Migration is a one-time, irreversible action. See "About migration"

    You can add different users as administrators to the Azure Sphere Tenant but Claiming is also a one-time operation that you cannot undo even if the device is sold or transferred to another person or organization. A device can be claimed only once. Once claimed, the device is permanently associated with the Azure Sphere tenant. See "Claim your device"

    Source: MSDN

    2 people found this answer helpful.
    0 comments No comments

0 additional answers

Sort by: Most helpful