Skip to content

Commit 1f6f0eb

Browse files
authored
Merge pull request #157905 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to master to sync with https://github.com/MicrosoftDocs/azure-docs (branch master)
2 parents 5f42098 + fcd3fd3 commit 1f6f0eb

File tree

2 files changed

+7
-5
lines changed

2 files changed

+7
-5
lines changed

articles/active-directory/develop/howto-configure-publisher-domain.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -82,14 +82,16 @@ If your app isn't registered in a tenant, you'll only see the option to verify a
8282

8383
1. Click the **Verify and save domain** button.
8484

85+
You're not required to maintain the resources that are used for verification after a domain has been verified. When the verification is finished, you can remove the hosted file.
86+
8587
### To select a verified domain
8688

87-
- If your tenant has verified domains, select one of the domains from the **Select a verified domain** dropdown.
89+
If your tenant has verified domains, select one of the domains from the **Select a verified domain** dropdown.
8890

89-
>[!Note]
90-
> The expected 'Content-Type' header that should be returned is `application/json`. You may get an error as mentioned below if you use anything else like `application/json; charset=utf-8`
91+
> [!NOTE]
92+
> The expected `Content-Type` header that should be returned is `application/json`. You may get an error as mentioned below if you use anything else, like `application/json; charset=utf-8`:
9193
>
92-
>``` "Verification of publisher domain failed. Error getting JSON file from https:///.well-known/microsoft-identity-association. The server returned an unexpected content type header value. " ```
94+
> `Verification of publisher domain failed. Error getting JSON file from https:///.well-known/microsoft-identity-association. The server returned an unexpected content type header value.`
9395
>
9496
9597
## Implications on the app consent prompt

includes/storage-quickstart-credentials-include.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ When the sample application makes a request to Azure Storage, it must be authori
1616

1717
1. Sign in to the [Azure portal](https://portal.azure.com).
1818
2. Locate your storage account.
19-
3. In the **Settings** section of the storage account overview, select **Access keys**. Here, you can view your account access keys and the complete connection string for each key.
19+
3. In the **Security + networking** section of the storage account overview, select **Access keys**. Here, you can view your account access keys and the complete connection string for each key.
2020
4. Find the **Connection string** value under **key1**, and select the **Copy** button to copy the connection string. You will add the connection string value to an environment variable in the next step.
2121

2222
![Screenshot showing how to copy a connection string from the Azure portal](./media/storage-copy-connection-string-portal/portal-connection-string.png)

0 commit comments

Comments
 (0)