Azure-docs: Missing step for Link storage accounts

[reneschulte]

This page is missing a needed step in order to be able to link the Storage accounts via IAM. The Remote Rendering resource first needs to enable Identity > System assigned > On. Otherwise no identity can be selected in the Storage accounts IAM Assign role dialog.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: d6c3c184-b242-c147-d7b6-609d237aa573
• Version Independent ID: ff5bf80a-0ed3-ada0-2b36-c7ce69d24ce5
• Content: Create an Azure Remote Rendering account - Azure Remote Rendering
• Content Source: articles/remote-rendering/how-tos/create-an-account.md
• Service: azure-remote-rendering
• GitHub Login: @FlorianBorn71
• Microsoft Alias: flborn

[FlorianBorn71]

Great, thanks for this feedback, very much appreciated!
I will check back with the devs and correct this.

[FlorianBorn71]

If you created your account after public preview release, then the system managed identity should be enabled by default. Older accounts however (created during private preview) may have this disabled. Does this maybe apply to you?
The migration guide during private preview strongly suggested to re-create the ARR account. If you fix the setting later (as you described above), then this may work at a first glance, but cause problems with storage accounts later on when trying to use them.

[reneschulte]

Hey @FlorianBorn71 That is not the case here.

I created the account freshly yesterday on a whole different tenant. All services were newly setup on my private Azure tenant yesterday and today. The private preview was using our company tenant.

[reneschulte]

Alright @FlorianBorn71 I just created a new ARR resource on the same private tenant and this one has Identity enabled by default.
You guys must have changed something in the last 30h or so.
The other one was created yesterday morning.

[FlorianBorn71]

glad to hear it works now!

[reneschulte]

Nope. Does not work. Somehow it was automatically disabled again.
Also just created a third instance and that did not have Identity On by default. Something is going on here.

[FlorianBorn71]

OK, will try to poll more information from the devs

[reneschulte]

I found out how to reproduce it:

1. Create new ARR resource with Azure Portal.
2. Go to Resource once deployed.
3. Click Identity and notice System assigned Status is on by default.
4. Click Access Keys to see the Primary Key, etc.
5. Click Identity and notice System assigned Status turned off now.

Turning it on manually seems to keep the state and does not switch it off when changing to another item.

Looks like a bug to me.

[FlorianBorn71]

Awesome, thanks for the repro steps! They helped pinpointing the underlying problem. The team is working on this.

[FlorianBorn71]

in-progress

[archanaiyer]

The fixes have been rolled out now.

• You should be able to turn the toggle in the Identity tab on/off.
• The identity tab doesn't change state when you switch between viewing other tabs (such as Access Keys)

Thank you for reporting the issue!

[reneschulte]

Confirmed it works now and the bug is fixed. Thanks and take care.