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: exchange/docs-conceptual/app-only-auth-powershell-v2.md
+67Lines changed: 67 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -291,6 +291,16 @@ After you register the certificate with your application, you can use the privat
291
291
292
292
### Step 5: Assign Azure AD roles to the application
293
293
294
+
You have two options:
295
+
296
+
-**Assign Azure AD roles to the application**: This method is supported in Exchange Online PowerShell and Security & Compliance PowerShell.
297
+
-**Assign custom Exchange Online role groups to the application**: Currently, this method is supported only in Exchange Online PowerShell, and only when you connect in [REST API mode](exchange-online-powershell-v2.md#updates-for-version-300-the-exo-v3-module) (don't use the _UseRPSSession_ switch in the **Connect-ExchangeOnline** command).
298
+
299
+
> [!NOTE]
300
+
> You can also combine both methods to assign permissions. Like using Azure AD roles for the "Exchange Recipient Administrator" role and assign your custom RBAC role to extend the permissions.
301
+
302
+
#### Assign Azure AD roles to the application
303
+
294
304
The supported Azure AD roles are described in the following table:
@@ -357,3 +367,60 @@ For general instructions about assigning roles in Azure AD, see [View and assign
357
367
-**Security & Compliance PowerShell**:
358
368
359
369

370
+
371
+
#### Assign custom Exchange Online role groups to the application
372
+
373
+
> [!NOTE]
374
+
> Remember, this method is supported only in Exchange Online PowerShell, and only when you connect in [REST API mode](exchange-online-powershell-v2.md#updates-for-version-300-the-exo-v3-module) (don't use the _UseRPSSession_ switch in the **Connect-ExchangeOnline** command).
375
+
376
+
For information about creating custom role groups, see [Create role groups](/exchange/permissions-exo/role-groups#create-role-groups). The custom role group that you assign to the application can contain any combination of built-in and custom roles.
377
+
378
+
To assign custom Exchange Online role groups to the application, do the following steps:
379
+
380
+
1. In [Azure Active Directory PowerShell for Graph](/powershell/azure/active-directory/install-adv2), run the following command to store the details of the Azure application that you registered in [Step 1](#step-1-register-the-application-in-azure-ad) in a variable:
Copy file name to clipboardExpand all lines: exchange/exchange-ps/exchange/Connect-ExchangeOnline.md
+21Lines changed: 21 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -33,6 +33,7 @@ Connect-ExchangeOnline
33
33
[[-Prefix] <String>]
34
34
[[-CommandName] <String[]>]
35
35
[[-FormatTypeName] <String[]>]
36
+
[-AccessToken <String>]
36
37
[-AppId <String>]
37
38
[-BypassMailboxAnchoring]
38
39
[-Certificate <X509Certificate2>]
@@ -280,6 +281,26 @@ Accept pipeline input: False
280
281
Accept wildcard characters: False
281
282
```
282
283
284
+
### -AccessToken
285
+
**Note**: This parameter is available in version 3.1.0-Preview1 or later of the module.
286
+
287
+
The AccessToken parameter specifies the OAuth JSON Web Token (JWT) that's used to connect to ExchangeOnline.
288
+
289
+
Depending on the type of access token, you need to use this parameter with the Organization, DelegatedOrganization, or UserPrincipalName parameter.
290
+
291
+
```yaml
292
+
Type: String
293
+
Parameter Sets: (All)
294
+
Aliases:
295
+
Applicable: Exchange Online
296
+
297
+
Required: False
298
+
Position: Named
299
+
Default value: None
300
+
Accept pipeline input: False
301
+
Accept wildcard characters: False
302
+
```
303
+
283
304
### -AppId
284
305
The AppId parameter specifies the application ID of the service principal that's used in certificate based authentication (CBA). A valid value is the GUID of the application ID (service principal). For example, `36ee4c6c-0812-40a2-b820-b22ebd02bce3`.
0 commit comments