Skip to content

Commit 96da55c

Browse files
committed
as per feedback from reviewer added a line to explain the screenshots
1 parent e86b9ef commit 96da55c

File tree

1 file changed

+6
-3
lines changed

1 file changed

+6
-3
lines changed

docs/legacy-protocols/how-to-authenticate-an-imap-pop-smtp-application-by-using-oauth.md

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -189,7 +189,8 @@ Service principals in Exchange are used to enable applications to access Exchang
189189

190190
4. Click **Application permissions**.
191191

192-
5. For POP access, choose the **POP.AccessAsApp** permission. For IMAP access, choose the **IMAP.AccessAsApp** permission. For SMTP access, choose the **SMTP.SendAsApp** permission.
192+
5. For POP access, choose the **POP.AccessAsApp** permission. For IMAP access, choose the **IMAP.AccessAsApp** permission. For SMTP access, choose the **SMTP.SendAsApp** permission.<br>
193+
The following screenshot shows the permissions selected:
193194

194195
![pop-imap-permission](media/pop-imap-smtp-permission.png)
195196

@@ -226,7 +227,9 @@ https://login.microsoftonline.com/{tenant}/v2.0/adminconsent?client_id=<CLIENT_I
226227

227228
If you registered your application in your own tenant using "Accounts in this organizational directory only", you can go forward and use the application configuration page within the Microsoft Entra admin center to grant the admin consent, and you don´t have to use the authorization request URL approach.
228229

229-
![granting-consent-for-tenant](media/grant-consent.png)
230+
The following screenshot shows how to grant admin consent using the application configuration page within the Microsoft Entra admin center.
231+
232+
:::image type="content" source="media/grant-consent.png" alt-text="Screenshot of how to grant admin consent." lightbox="media/grant-consent.png":::
230233

231234
### Register service principals in Exchange
232235

@@ -258,7 +261,7 @@ Get-ServicePrincipal | fl
258261

259262
The OBJECT_ID is the Object ID from the Overview page of the Enterprise Application node (Azure Portal) for the application registration. It is **not** the Object ID from the Overview page of the App Registrations node. Using the incorrect Object ID will cause an authentication failure.
260263

261-
The following example finds the correct Object ID, which begins with '6d':
264+
The following screenshot shows an example that finds the correct Object ID, which begins with '6d':
262265

263266
:::image type="content" source="media/object-id.png" alt-text="Screenshot of example of finding the correct object id." lightbox="media/object-id.png":::
264267

0 commit comments

Comments
 (0)