Merge pull request #127805 from baanders/8-31-fix

ADT- Mobile/desktop registration

Author: Jak-MS

articles/digital-twins/how-to-set-up-instance-cli.md

@@ -119,7 +119,7 @@ Next, you'll upload this file to Cloud Shell. In your Cloud Shell window, click
 :::image type="content" source="media/how-to-set-up-instance/cloud-shell/cloud-shell-upload.png" alt-text="Cloud Shell window showing selection of the Upload option":::
 Navigate to the *manifest.json* you just created and hit "Open."
 
-Next, run the following command to create an app registration (replacing placeholders as needed):
+Next, run the following command to create an app registration, with a *Public client/native (mobile & desktop)* reply URL of `http://localhost`. Replace placeholders as needed:
 
 ```azurecli
 az ad app create --display-name <name-for-your-app-registration> --native-app --required-resource-accesses manifest.json --reply-url http://localhost

articles/digital-twins/how-to-set-up-instance-portal.md

@@ -108,7 +108,7 @@ Start by navigating to [Azure Active Directory](https://portal.azure.com/#blade/
 In the *Register an application* page that follows, fill in the requested values:
 * **Name**: An Azure AD application display name to associate with the registration
 * **Supported account types**: Select *Accounts in this organizational directory only (Default Directory only - Single tenant)*
-* **Redirect URI**: An *Azure AD application reply URL* for the Azure AD application. You can use `http://localhost`.
+* **Redirect URI**: An *Azure AD application reply URL* for the Azure AD application. Add a *Public client/native (mobile & desktop)* URI for `http://localhost`.
 
 When you are finished, hit the *Register* button.
 

articles/digital-twins/how-to-set-up-instance-scripted.md

@@ -56,7 +56,7 @@ Here are the steps to run the deployment script in Cloud Shell.
     * For the instance: a *resource group* name. You can use an existing resource group, or enter a new name of one to create.
     * For the instance: a *name* for your Azure Digital Twins instance. The name of the new instance must be unique within the region for your subscription (meaning that if your subscription has another Azure Digital Twins instance in the region that's already using the name you choose, you'll be asked to pick a different name).
     * For the app registration: an *Azure AD application display name* to associate with the registration. This app registration is where you configure access permissions to the [Azure Digital Twins APIs](how-to-use-apis-sdks.md). Later, the client app will authenticate against the app registration, and as a result be granted the configured access permissions to the APIs.
-    * For the app registration: an *Azure AD application reply URL* for the Azure AD application. You can use `http://localhost`.
+    * For the app registration: an *Azure AD application reply URL* for the Azure AD application. Use `http://localhost`. The script will set up a *Public client/native (mobile & desktop)* URI for it.
 
 The script will create an Azure Digital Twins instance, assign your Azure user the *Azure Digital Twins Owner (Preview)* role on the instance, and set up an Azure AD app registration for your client app to use.