MT3620 Azure Sphere Dev Kit

Tom S 41 Reputation points
2022-10-04T10:44:05.89+00:00

I have used this device MT3620 Development Kit.

I created a tenant before with an onmicrosoft.com account and I have the name and id of the tenant recorded. The device was successfully claimed.

I can perform the command azsphere select and use the id for the tenant I recorded previously.
Then the azsphere tenant show-selected returns that Id and Name .

However the list command never shows this tenant. And I get errors that the tenant does not have the device.
Like I said, I can still select my tenant but it is not in the list. If it is a problem with access permissions how do I change them. I still have device id , tenant id , and login so why did it stop working. Migrate command not available. I want to use the device,

I understand it can only be claimed once. That is what I did and have the claim tenant and id with device id.
What I don't understand is how a piece of hardware now will not let me download new programs because I have not used it for a while.

It shows version 22.09.
What is wrong here and how can I fix it?

Thanks

Azure Sphere
Azure Sphere
An Azure internet of things security solution including hardware, operating system, and cloud components.
168 questions
{count} votes

Accepted answer
  1. QuantumCache 20,271 Reputation points
    2022-10-18T18:33:30.477+00:00

    Hello all,

    We are posting some of the offline conversations on this topic, so that it is useful to other readers.

    Scenario: Given that you last used the device in 2019, before the Azure Sphere GA date, it's possible that you have not migrated your tenant to the production system, therefor your device was not carried over. This is no-longer possible automatically. We can look to do this manually for you but need to establish proof-of-possession of both the device and tenant. Once the proof-of-possession is successful, you will hopefully have access to your tenant/device restored, otherwise unfortunately there won't be any further action we can take on this matter. Below details are needed to be provided to the Microsoft's Support Team to verify the proof-of-possession.

    • The device ID
    • The tenant ID
    • User account identifiers such as email.

    After looking into this issue, the product team were able to identify sufficient proof-of-ownership to restore access, the account should now be attached to the tenant as an administrator.

    I hope this has resolved your issue.

    If the response is helpful, please click "Accept Answer" and upvote it. So that we can close this thread.

    1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
  1. Tom S 41 Reputation points
    2022-10-04T22:07:34.117+00:00

    azsphere device show-deployment-status

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

    azsphere tenant select -t xxxxxxxx=xxxx=xxxx=xxxxxxxxxxx

    returns
    Id Name
    xxxxxxxx=xxxx=xxxx=xxxxxxxxxxx MyTenantName

    azsphere device show-deployment-status

    Your device is running Azure Sphere OS version 22.09.
    Could not retrieve details for this device in the current Azure Sphere tenant.
    Try 'azsphere device claim'
    Ensure that you have the right permissions to execute this command in the selected Azure Sphere tenant.
    Please see https://aka.ms/AzureSphereSDKHelp/Cloud for troubleshooting or suggestions.
    Trace ID: a96d9299-8d57-479d-b9d3-272a73ba06da

    azsphere tenant select -t xxxxxxxx=xxxx=xxxx=xxxxxxxxxxx --verbose

    with verbose I get following

    Azure Sphere Utility version 22.9.4.54546
    Copyright (C) Microsoft Corporation. All rights reserved.

    Start time (UTC): Tuesday, 04 October 2022 22:01:29
    No SerialSlipToTunService port is set in the registry; defaulting to 48938.
    No SerialSlipToTunService port is set in the registry; defaulting to 48938.
    Downloading OS image set data from https://prod.releases.sphere.azure.net/versions/mt3620an.json.
    Your device is running Azure Sphere OS version 22.09.
    ==> Using your default Azure Active Directory tenant.
    ==> Using environment: 'prod'.
    ==> Using Azure Sphere tenant ID: 'xxxxxxxx=xxxx=xxxx=xxxxxxxxxxx'.

    No SerialSlipToTunService port is set in the registry; defaulting to 48938.
    Using attached device ID 'The device id here ... long number'.
    TraceId: baf4b8d0-a969-4787-9fed-c21d1b5f0af5
    Could not retrieve details for this device in the current Azure Sphere tenant.
    Try 'azsphere device claim'

    It has been claimed before but for fun I try to claim it again

    Claiming device.
    TraceId: 4cd772a3-c442-4310-b5d6-7b82685e9322
    Response content: "Error occurred while claiming device for device id "the device id a
    long number, tenantId mytenantid number."
    Failed to claim device ' to this Azure Sphere tenant.
    This may be because it was already claimed to a different Azure Sphere tenant or because you don't have the right permissions to execute this command in the selected Azure Sphere tenant.

    So in summary there is a tenant on the device.. it has been claimed ... just the tenant and id not matched up now??

    1 person found this answer helpful.
    0 comments No comments

Your answer

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