Skip to content

Commit c1ecfc1

Browse files
authored
Merge pull request #74767 from secherka/patch-9
Update howto-configure-publisher-domain.md
2 parents caef467 + 35be4c1 commit c1ecfc1

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
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

0 commit comments

Comments
 (0)