Horrible experience so far trying to use the Azure Sphere kit

I managed to set mine up, but I do have to agree that the documentation can be slightly difficult to follow and the order in which it is presented can be confusing. There are also minor errors in the documentation as well.

Consumer Microsoft accounts don't work as they aren't backed by an active directory. Workplace/University accounts may work, but if they are not provisioned for Azure, then you could end up stuck like this person: https://www.element14.com/community/message/278030/l/re-failed-to-create-an-azure-sphere-tenant#278030

Ideally, you should create a new account that is in the form of <name>@<domain>.onmicrosoft.com via this page (https://account.azure.com/organization ) linked here: https://docs.microsoft.com/en-us/azure-sphere/install/azure-directory-account. Towards the end of the process, it might ask you to sign into your existing account but it didn't work for me - but it did generate a new account which I could then use with the Azure Sphere Developer SDK.

In the Azure Sphere Developer Command Prompt, you should then be able to use the 'azsphere login' command, using the username of <name>@<domain>.onmicrosoft.com and the password you selected. If successful, then everything else should work including creating a tenant and claiming a device. Note that the show-ota-status doesn't work until the device has been claimed (as far as I know) and this is a "bug" with the documentation (i.e. OS updates cannot happen until claimed - but automatic updates do work, just give it some time).

- Gough

G'Day,

Your experience is frustrating to say the least. It sounds like to me, your RoadTest project is like playing the text based version of the game Dungeons and Dragons. Turn left: Ugh crap, I walked over a cliff. Restart. Turn right: Ugh crap the monster got me! Each and every step might be a clue or is just another path leading you to destruction. Be nice to know you can be successful?

I would encourage you continue to documenting your trials and tribulations. Your experiences on paper is the next best things to completing the project to your satisfaction. That may seem like poor consultation but given my understanding (very limited) of the program, you are providing the Element14 team insight that can be used to improve the program.

I'm going to take the glass half full view instead of half empty in my commentary. The half empty commentary is more my style so I might be full of sh#*. The RoadTest team puts considerable effort into ensuring its participates supply appropriate applications and deliver on their promise of a RoadTest review. I suspect they have to do the same on the vendor side or the program will fail. Maybe a blog on your moves along the path of failed expectations is not such a bad thing?

To me your experience also highlights questions RoadTesters need to ask themselves. What are your expectations? What do you require in deliver on those expectations? What is your plan if you are forced to come up short on your expectations? I suspect we all enter RoadTests with visions of success. Few if any of us think about failures.

A well documented failure can have value. Unfortunately, it can take a lot of time and will fail to meet most expectations.

Sean

Hi Cosmin,

You are one of the most skilled and competent engineers I know and if you are having troubles with this it has to be a red flag to the developers that they have some serious problems. Thanks for sharing your frustration. It could be that they are aware of the trouble and are hoping the field can give them some solutions.

John

You are very close!  Here is an example command line entry for creating a tenant:

azsphere tenant create --name MyTenant

The --name has to be typed out explicitly before the name you make up is typed.  MyTenant is just something I made up.  Change that to something you think is cool.

I was able to make it through the 3 tutorials.  I felt the typical frustration I always get when I use Linux in general on Micro Controllers such as a headless Raspberry PI or PocketBeagle.  Goofy syntax, oddball descriptions in the help, uncooperative updates, a lot of copy pasting of strings from files I can never locate, etc.

I can't say I'd pin the frustration on the Azure Sphere, but rather the 80's world we are back in with this hardware since the speeds are slow and the RAM is low - forcing us back down below where Python and Windows have concealed us from for so many years now.  But, to be honest, its that 80's vibe that makes me enjoy it.  :-)

In the comments of each of the 3 tutorials, I documented the errata I found.  It may be helpful to scroll down to the comments before you begin.

See ya',

Sean

Cosmin,

I found this guide wasn't too bad but there are a couple of quirks: https://docs.microsoft.com/en-us/azure-sphere/install/overview

Firstly, the "Update OS" needs to be done later in the process, as at this point the device isn't registered.

Secondly, creating a "work/school account" is a bit confusing for most of us who will be using a personal account. It does work if you follow it, but it isn't very clear.

I was about to raise these issues on the page but I can see someone else has already done so. I hope it will be updated soon to be a little clearer for those new to Azure.

Hi John, thank you for the nice comments.

Best Wishes,

Cosmin

Hi Gough,

Thank you for your help.  I will take a look at the links and hopefully I can get this thing to work.

Best Wishes,

Cosmin

Thank you Sean.  The command azsphere tenant create --name MyTenant with my name in there worked.   Thank you also for the link to the tutorials.

Best Wishes,

Cosmin

Thank you David for this info.  I will use it as reference for the next steps in my work with this kit.

Best Wishes,

Cosmin