You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/legacy-protocols/how-to-authenticate-an-imap-pop-smtp-application-by-using-oauth.md
+6-3Lines changed: 6 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -189,7 +189,8 @@ Service principals in Exchange are used to enable applications to access Exchang
189
189
190
190
4. Click **Application permissions**.
191
191
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:
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.
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":::
230
233
231
234
### Register service principals in Exchange
232
235
@@ -258,7 +261,7 @@ Get-ServicePrincipal | fl
258
261
259
262
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.
260
263
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':
262
265
263
266
:::image type="content" source="media/object-id.png" alt-text="Screenshot of example of finding the correct object id." lightbox="media/object-id.png":::
0 commit comments