Merge pull request #237398 from MichaelZp0/MichaelZp0/AdjustJsonContentsToReflectNewRenderingSessionPs1Syntax

Switched from Region to Domain properties everywhere

Author: prmerger-automator[bot]

articles/remote-rendering/how-tos/create-an-account.md

@@ -24,16 +24,16 @@ The following steps are needed to create an account for the Azure Remote Renderi
     1. Set 'Resource Name' to the name of the account
     1. Update 'Subscription' if needed
     1. Set 'Resource group' to a resource group of your choice
-    1. Select a region from the 'Location' dropdown where this resource should be created in. See remarks on [account regions](create-an-account.md#account-regions) below.
+    1. Select a region from the 'Location' dropdown where this resource should be created in. See remarks on [account regions](create-an-account.md#account-regions).
 1. Once the account is created, navigate to it and:
     1. In the *Overview* tab, note the 'Account ID'
-    1. In the *Settings > Access Keys* tab, note the 'Primary key' - this is the account's secret account key
+    1. In the *Settings > Access Keys* tab, note the 'Primary key' - this value is the account's secret account key
     1. Make sure, that in the *Settings > Identity* tab, the option *System assigned > Status* is turned on.
 
 :::image type="content" source="./media/azure-identity-add.png" alt-text="Screenshot of Remote Rendering Account Page in sub menu settings, identity, with the option System assigned status turned on.":::
 
 ### 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](./../reference/regions.md), regardless of the account's location.
+The location that is specified during account creation time of an account determines which region the account resource is assigned to. The location can't be changed after creation. However, the account can be used to connect to a Remote Rendering session in any [supported region](./../reference/regions.md), regardless of the account's location.
 
 ### Retrieve the account information
 
@@ -43,11 +43,11 @@ The samples and tutorials require that you provide the account ID and a key. For
 "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>"
+    "arrAccountDomain": "<select from available regions: australiaeast, eastus, eastus2, japaneast, northeurope, southcentralus, southeastasia, uksouth, westeurope, westus2 or specify the full url>"
 },
 ```
 
-See the [list of available regions](../reference/regions.md) for filling out the *region* option.
+See the [list of available regions](../reference/regions.md) for filling out the *arrAccountDomain* option.
 
 The values for **`arrAccountId`** and **`arrAccountKey`** can be found in the portal as described in the following steps:
 
@@ -68,21 +68,21 @@ The value for **`arrAccountKey`** can either be primary or secondary key.
 
 ## Link storage accounts
 
-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](../concepts/models.md#loading-models).
+This paragraph explains how to link storage accounts to your Remote Rendering account. With a linked account, it isn't necessary anymore to generate a SAS URI every time you want to interact with the data in your account. Instead, you can use the storage account names directly as described in the [loading a model section](../concepts/models.md#loading-models).
 
 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](../quickstarts/convert-model.md#storage-account-creation).
 
 1. Navigate to your storage account in the Azure portal
 
-1. Select **Access control (IAM)**.
+2. Select **Access control (IAM)**.
 
-1. Select **Add** > **Add role assignment** to open the **Add role assignment** page.
+3. Select **Add** > **Add role assignment** to open the **Add role assignment** page.
 
-   If you don't have owner permissions to this storage account, the **Add a role assignment** option will be disabled.
+   If the **Add a role assignment** option is disabled, you probably don't have owner permissions to this storage account.
 
-1. Assign the following role. For detailed steps, see [Assign Azure roles using the Azure portal](../../role-based-access-control/role-assignments-portal.md).
+4. Assign the following role. For detailed steps, see [Assign Azure roles using the Azure portal](../../role-based-access-control/role-assignments-portal.md).
    1. Select the **Storage Blob Data Contributor** role and click **Next**.
-   1. Choose to assign access to a **Managed Identity**. 
+   1. Choose to assign access to a **Managed Identity**.
    1. Select **Select members**, select your subscription, select **Remote Rendering Account**, select your remote rendering account, and then click **Select**.
    1. Select **Review + assign** and select **Review + assign** again.
 

articles/remote-rendering/quickstarts/convert-model.md

@@ -10,9 +10,9 @@ ms.custom: devx-track-azurepowershell, mode-other
 
 # Quickstart: Convert a model for rendering
 
-In [Quickstart: Render a model with Unity](render-model.md), you learned how to use the Unity sample project to render a built-in model. This guide shows how to convert your own models.
+In [Quickstart: Render a model with Unity](render-model.md), you learned how to use the Unity sample project to render a built-in model.
 
-You'll learn how to:
+This guide shows how to convert your own models, entailing these steps:
 
 > [!div class="checklist"]
 >
@@ -51,6 +51,7 @@ Once you have an Azure account, go to [https://portal.azure.com/#home](https://p
 ### Storage account creation
 
 To create blob storage, you first need a storage account.
+
 1. To create one, select "Create a resource":
 
 ![Azure - add resource](media/azure-add-a-resource.png)
@@ -59,30 +60,30 @@ To create blob storage, you first need a storage account.
 
 ![Azure - add storage](media/azure-add-storage.png)
 
-3. Clicking this button will bring up the following screen with storage properties to fill out:
+3. Clicking this button brings up the following screen with storage properties to fill out:
 
 ![Azure Setup](media/azure-setup1.png)
 
 4. Fill out the form in the following manner:
 
 * Create a new Resource Group from the link below the drop-down box and name this **ARR_Tutorial**
-* For the **Storage account name**, enter a unique name here. **This name must be globally unique**, otherwise there will be a prompt that informs you that the name is already taken. In the scope of this quickstart, we name it **arrtutorialstorage**. Accordingly, you need to replace it with your name for any occurrence in this quickstart.
+* For the **Storage account name**, enter a unique name here. **This name must be globally unique**. An error message is shown if the name is already taken. In the scope of this quickstart, we name it **arrtutorialstorage**. Accordingly, you need to replace it with your name for any occurrence in this quickstart.
 * Select a **Region** close to you. Ideally use the same [region](../reference/regions.md) as used for setting up the rendering in the other quickstart.
-* **Performance** set to 'Premium'. 'Standard' works as well, but has lower loading time characteristics when a model is loaded by the runtime.
+* **Performance** set to 'Premium'. 'Standard' works as well, but has lower loading time characteristics when loading a model.
 * **Premium account type** set to 'Block blobs'
 * **Redundancy** set to 'Zone-redundant storage (ZRS)'
 
-5. None of the properties in other tabs have to be changed, so you can proceed with **"Review + create"** and then follow the steps to complete the setup.
+1. None of the properties in other tabs have to be changed, so you can proceed with **"Review + create"** and then follow the steps to complete the setup.
 
-6. The website now informs you about the progress of your deployment and reports "Your deployment is complete" eventually. Select **"Go to resource"** for the next steps:
+2. The website now informs you about the progress of your deployment and reports "Your deployment is complete" eventually. Select **"Go to resource"** for the next steps:
 
 ![Azure Storage creation complete](./media/storage-creation-complete.png)
 
 ### Blob storage creation
 
 Next we need two blob containers, one for input and one for output.
 
-1. From the **"Go to resource"** button above, you get to a page with a panel on the left that contains a list menu. In that list under the **"Blob service"** category, select **"Containers"**:
+1. From the **"Go to resource"** button, you get to a page with a panel on the left that contains a list menu. In that list under the **"Blob service"** category, select **"Containers"**:
 
 ![Azure - add Containers](./media/azure-add-containers.png)
 
@@ -117,7 +118,8 @@ To make it easier to call the asset conversion service, we provide a utility scr
 In particular, this script
 
 * uploads all files in a given directory from local disk to the input storage container,
-* calls the [the asset conversion REST API](../how-tos/conversion/conversion-rest-api.md), which will retrieve the data from the input storage container and start a conversion, which will return a conversion ID,
+* calls the [asset conversion REST API](../how-tos/conversion/conversion-rest-api.md)
+  * this api retrieves the data from the input storage container, starts a conversion and returns a conversion ID,
 * polls the conversion status API with the retrieved conversion ID until the conversion process terminates with success or failure,
 * retrieves a link to the converted asset in the output storage.
 
@@ -128,11 +130,10 @@ The script reads its configuration from the file *Scripts\arrconfig.json*. Open
     "accountSettings": {
         "arrAccountId": "8*******-****-****-****-*********d7e",
         "arrAccountKey": "R***************************************l04=",
-        "region": "<your-region>"
+        "arrAccountDomain": "<select from available regions: australiaeast, eastus, eastus2, japaneast, northeurope, southcentralus, southeastasia, uksouth, westeurope, westus2 or specify the full url>"
     },
     "renderingSessionSettings": {
-        "vmSize": "standard",
-        "maxLeaseTime": "1:00:00"
+        "remoteRenderingDomain": "<select from available regions: australiaeast, eastus, eastus2, japaneast, northeurope, southcentralus, southeastasia, uksouth, westeurope, westus2 or specify the full url>"
     },
     "assetConversionSettings": {
         "localAssetDirectoryPath": "D:\\tmp\\robot",
@@ -148,20 +149,22 @@ The script reads its configuration from the file *Scripts\arrconfig.json*. Open
 }
 ```
 
-The configuration within the **accountSettings** group (account ID and key) should be filled out analogous to the credentials in the [Render a model with Unity quickstart](render-model.md).
+The configuration within the **accountSettings** group (account ID, key and domain) should be filled out analogous to the credentials in the [Render a model with Unity quickstart](render-model.md).
+
+A full configuration of the **renderingSessionSettings** group (domain, vmSize and maxLeaseTime) can be seen in [PowerShell Example scripts](../samples/powershell-example-scripts.md). The vmSize and maxLeaseTime aren't important for conversion and can be omitted, as they don't affect the conversion.
 
-Inside the **assetConversionSettings** group, make sure to change **resourceGroup**, **blobInputContainerName**, and **blobOutputContainerName** as seen above.
+Inside the **assetConversionSettings** group, make sure to change **resourceGroup**, **blobInputContainerName**, and **blobOutputContainerName**.
 The value for **arrtutorialstorage** needs to be replaced with the unique name you picked during storage account creation.
 
 Change **localAssetDirectoryPath** to point to the directory on your disk, which contains the model you intend to convert. Be careful to properly escape backslashes ("\\") in the path using double backslashes ("\\\\").
 
-All data from the path given in **localAssetDirectoryPath** will be uploaded to the **blobInputContainerName** blob container under a subpath given by **inputFolderPath**. So in the example configuration above the content of the "D:\\tmp\\robot" directory will be uploaded to the blob container "arrinput" of the storage account "arrtutorialstorage" under the path "robotConversion". Already existing files will be overwritten.
+The service uploads all data from the path given in **localAssetDirectoryPath** to the **blobInputContainerName** blob container under a subpath given by **inputFolderPath**. With the example configuration, the service uploads the content of the "D:\\tmp\\robot" directory to the blob container "arrinput" of the storage account "arrtutorialstorage" under the path "robotConversion". Already existing files are overwritten.
 
 Change **inputAssetPath** to the path of the model to be converted - the path is relative to localAssetDirectoryPath. Use "/" instead of "\\" as the path separator. So for a "robot.fbx" file, which is located directly in "D:\\tmp\\robot", use "robot.fbx".
 
-Once the model was converted, it will be written back to the storage container given by **blobOutputContainerName**. A subpath can be specified by providing the optional **outputFolderPath**. In the example above, the resulting "robot.arrAsset" will be copied to the output blob container under "converted/robot".
+Once the model was converted, it's written back to the storage container given by **blobOutputContainerName**. A subpath can be specified by providing the optional **outputFolderPath**. In the example, the service copies the resulting "robot.arrAsset" to the output blob container under "converted/robot".
 
-The config setting **outputAssetFileName** determines the name of the converted asset - the parameter is optional and the output filename will be deduced from the input file name otherwise.
+The config setting **outputAssetFileName** determines the name of the converted asset - the parameter is optional and if not specified the service uses the input file name to generate an output name.
 
 Open a PowerShell, make sure you installed the *Azure PowerShell* as mentioned in the [prerequisites](#prerequisites). Then log into your subscription with the following command and follow the on-screen directions:
 
@@ -198,7 +201,7 @@ The conversion script generates a *Shared Access Signature (SAS)* URI for the co
 
 ## Optional: Re-creating a SAS URI
 
-The SAS URI created by the conversion script will only be valid for 24 hours. However, after it expired you don't need to convert your model again. Instead, you can create a new SAS in the portal as described in the next steps:
+The SAS URI created by the conversion script expires after 24 hours. However, after it expired you don't need to convert your model again. Instead, you can create a new SAS in the portal as described in the next steps:
 
 1. Go to the [Azure portal](https://www.portal.azure.com)
 2. Select your **Storage account** resource:

articles/remote-rendering/samples/powershell-example-scripts.md

@@ -37,7 +37,7 @@ To execute the sample scripts, you need a functional setup of [Azure PowerShell]
 
 1. [Prepare an Azure Storage account](../how-tos/conversion/blob-storage.md#prepare-azure-storage-accounts)
 
-1. Log into your subscription containing your Azure Remote Rendering account:
+1. Log in to your subscription containing your Azure Remote Rendering account:
     1. Open a PowerShell window.
     1. Run: `Connect-AzAccount` and follow the on-screen directions.
 
@@ -55,10 +55,10 @@ Next to the `.ps1` files there's an `arrconfig.json` that you need to fill out:
     "accountSettings": {
         "arrAccountId": "<fill in the account ID from the Azure Portal>",
         "arrAccountKey": "<fill in the account key from the Azure Portal>",
-        "arrAccountDomain": "<select from available regions or specify the full url>"
+        "arrAccountDomain": "<select from available regions: australiaeast, eastus, eastus2, japaneast, northeurope, southcentralus, southeastasia, uksouth, westeurope, westus2 or specify the full url>"
     },
     "renderingSessionSettings": {
-        "remoteRenderingDomain": "<select from available regions or specify the full url>",
+        "remoteRenderingDomain": "<select from available regions: australiaeast, eastus, eastus2, japaneast, northeurope, southcentralus, southeastasia, uksouth, westeurope, westus2 or specify the full url>",
         "vmSize": "<select standard or premium>",
         "maxLeaseTime": "<hh:mm:ss>"
     },
@@ -85,7 +85,7 @@ Next to the `.ps1` files there's an `arrconfig.json` that you need to fill out:
 ### accountSettings
 
 For `arrAccountId` and `arrAccountKey`, see [Create an Azure Remote Rendering account](../how-tos/create-an-account.md).
-The `arrAccountDomain` should be a region from [list of available regions](../reference/regions.md). If you're running on a nonpublic Azure region, you have to specify the full url to the account authentication service in your region.
+The `arrAccountDomain` should be a region from [list of available regions](../reference/regions.md).
 
 ### renderingSessionSettings
 
@@ -95,7 +95,6 @@ This structure must be filled out if you want to run **RenderingSession.ps1**:
 - **maxLeaseTime:** The duration for which you want to lease the VM. The VM shuts down when the lease expires. The lease time can be extended later (see [here](#change-session-properties)).
 - **remoteRenderingDomain:** The region where the remote rendering VM resides in.
   - Can differ from the arrAccountDomain, but still should be a region from [list of available regions](../reference/regions.md)
-  - If you're running on a nonpublic Azure region, you have to specify the full url to the remote rendering service in your region.
 
 ### assetConversionSettings
 
@@ -187,7 +186,7 @@ The script demonstrates the two options to use storage accounts with the service
 
 ### Linked storage account
 
-Once you've fully filled out arrconfig.json and linked a storage account, you can use the following command. Linking your storage account is described at [Create an Account](../how-tos/create-an-account.md#link-storage-accounts).
+Once you have fully filled out arrconfig.json and linked a storage account, you can use the following command. Linking your storage account is described at [Create an Account](../how-tos/create-an-account.md#link-storage-accounts).
 
 Using a linked storage account is the preferred way to use the conversion service since there's no need to generate Shared Access Signatures.