Create an Azure Remote Rendering account

This chapter guides you through the steps to create an account for the Azure Remote Rendering service. A valid account is mandatory for completing any of the quickstarts or tutorials.

Create an account

The following steps are needed to create an account for the Azure Remote Rendering service:

  1. Go to the Mixed Reality Preview page
  2. Click the 'Create a resource' button
  3. In the search field ("Search the marketplace"), type in "Remote Rendering" and hit 'enter'.
  4. In the result list, click on the "Remote Rendering" tile
  5. In the next screen, click the "Create" button. A form opens to create a new Remote Rendering account:
    1. Set 'Resource Name' to the name of the account
    2. Update 'Subscription' if needed
    3. Set 'Resource group' to a resource group of your choice
    4. Select a region from the 'Location' dropdown where this resource should be created in. See remarks on account regions below.
  6. Once the account is created, navigate to it and:
    1. In the Overview tab, note the 'Account ID'
    2. In the Settings > Access Keys tab, note the 'Primary key' - this is the account's secret account key

Account regions

The location that is specified during account creation time of an account determines which region the account resource is assigned to. This cannot be changed after creation. However, the account can be used to connect to a Remote Rendering session in any supported region, regardless of the account's location.

Retrieve the account information

The samples and tutorials require that you provide the account ID and a key. For instance in the arrconfig.json file that is used for the PowerShell sample scripts:

"accountSettings": {
    "arrAccountId": "<fill in the account ID from the Azure portal>",
    "arrAccountKey": "<fill in the account key from the Azure portal>",
    "region": "<select from available regions>"

See the list of available regions for filling out the region option.

The values for arrAccountId and arrAccountKey can be found in the portal as described in the following steps:

  • Go to the Azure portal
  • Find your "Remote Rendering Account" - it should be in the "Recent Resources" list. You can also search for it in the search bar at the top. In that case, make sure that the subscription you want to use is selected in the Default subscription filter (filter icon next to search bar):

Subscription filter

Clicking on your account brings you to this screen, which shows the Account ID right away:

Azure account ID

For the key, select Access Keys in the panel on the left. The next page shows a primary and a secondary key:

Azure access keys

The value for arrAccountKey can either be primary or secondary key.

This paragraph explains how to link storage accounts to your Remote Rendering account. When a storage account is linked it is not necessary to generate a SAS URI every time you want to interact with the data in your account, for instance when loading a model. Instead, you can use the storage account names directly as described in the loading a model section.

The steps in this paragraph have to be performed for each storage account that should use this access method. If you haven't created storage accounts yet, you can walk through the respective step in the convert a model for rendering quickstart.

Now it is assumed you have a storage account. Navigate to the storage account in the portal and go to the Access Control (IAM) tab for that storage account:

Storage account IAM

Ensure you have owner permissions over this storage account to ensure that you can add role assignments. If you don't have access, the Add a role assignment option will be disabled.

Click on the Add button in the "Add a role assignment" tile to add the role.

Storage account IAM add role assignment

  • Assign Storage Blob Data Contributor role as shown in the screenshot above.
  • Select Remote Rendering Account system assigned managed identity from the Assign access to dropdown.
  • Select your subscription and Remote Rendering account in the last dropdowns.
  • Click "Save" to save your changes.


In case your Remote Rendering account is not listed, refer to this troubleshoot section.


Azure role assignments are cached by Azure Storage, so there may be a delay of up to 30 minutes between when you grant access to your remote rendering account and when it can be used to access your storage account. See the Azure role-based access control (Azure RBAC) documentation for details.

Next steps