Possible faulty Azure Sphere device

Thanks for all the suggestions.

I have been through the documentation and the troubleshooting guide suggested by Brian and the guide suggested by Fred but all is setup as suggested.

The issue I have is that the device is now out of the box.

I have setup my AAD properly and also created an account to use with the Global Admin role applied.

When I issue the azsphere login command with that account I get the following which is expected as I haven't created the tenant yet but proves the account is working:

warn: No Azure Sphere tenants found under the selected AAD user.

Successfully logged in with the selected AAD user. This authentication will be used for subsequent commands.

Command completed successfully in 00:00:10.6725886.

Next I do the logical thing and try to create my tenant but this is what is returned:

error: Failed to create an Azure Sphere tenant with name 'AzureSphere'.

Trace ID: acc4be19-6a9f-4133-9fde-073e92f6100b

error: An unexpected problem occurred. Please try again; if the issue persists, please refer to aka.ms/azurespheresupport for troubleshooting suggestions and support.

error: Command failed in 00:00:19.5623966.

I have tried using names with spaces, without spaces, with quotes and without and tried random names in case I have hit some reserved term.

I have also tried using the force option and added verbose to see if the logging tells me anything.

Nothing results in a different outcome and the logging just gives me a very long winded "400 Bad Request" result.

I can run the command "azsphere dev show-attached" and get a result describing the device ID and its IP so the comms to the device seems good.

If I log into a different Azure account that I know does already have a tenant created and run the following command I have seen Microsoft suggesting tells us if the device has been pre claimed all seems good.

azsphere dev show-ota-status

Your device is running Azure Sphere OS version 19.07.

error: An unexpected problem occurred. Please try again; if the issue persists, please refer to aka.ms/azurespheresupport for troubleshooting suggestions and support.

error: Command failed in 00:00:03.1368024.

Based on Microsofts suggestions it seems this confirms its not claimed.

So what next?

You can only claim a device once and I haven't claimed it anywhere and it seems the above confirms that.

You can only use the device to create one tenant, I haven't created a tenant yet. The account where I had access to a tenant was seeing a tenant created by someone else.

The account with access to a tenant is in a completely different AAD than the one where I'm unable to create a tenant, so different AADs and different accounts.

The reason I suspected hardware is due to MS saying that you can only create a tenant with a device attached and you can only use a device to create a single tenant.

That to me means that something in the devices identity is used to create that tenant and if the device isn't responding properly then that's going to cause a Bad Request response, all supposition but the best I have right now.

I have already run an "azsphere dev recover" to ensure the OS version on the device is up to date and that seems to succeed.

I have checked my AAD config and can see that the 2 Azure Sphere Applications (API and Utility) are listed.

In short I have now run out of places to look and wonder if anyone else can suggest anything or if we think it is a hardware issue does anyone know how Azure Sphere returns work?

Thanks for the detailed response.

Firstly, while logged into each id you used or created, issue:

• azsphere tenant list
• azsphere tenant selected

Then drop in the results here. What we need is the Guid's and names associated with them

Thanks,

Clem

BTW, I worked with multiple devices and learned the hard way how to deal with issues.

BTW, I worked with multiple devices and learned the hard way how to deal with issues.