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
+14-14Lines changed: 14 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -129,7 +129,7 @@ The following examples show how to use the Exchange Online PowerShell module wit
129
129
130
130
## Set up app-only authentication
131
131
132
-
An initial onboarding is required for authentication using application objects. Application and service principal are used interchangeably, but an application is like a class object while a service principal is like an instance of the class. For more information, see [Application and service principal objects in Microsoft Entra ID](/azure/active-directory/develop/app-objects-and-service-principals).
132
+
An initial onboarding is required for authentication using application objects. Application and service principal are used interchangeably, but an application is like a class object while a service principal is like an instance of the class. For more information, see [Application and service principal objects in Microsoft Entra ID](/entra/identity-platform/app-objects-and-service-principals).
133
133
134
134
For a detailed visual flow about creating applications in Microsoft Entra ID, see <https://aka.ms/azuread-app>.
135
135
@@ -159,7 +159,7 @@ For a detailed visual flow about creating applications in Microsoft Entra ID, se
159
159
### Step 1: Register the application in Microsoft Entra ID
160
160
161
161
> [!NOTE]
162
-
> If you encounter problems, check the [required permissions](/azure/active-directory/develop/howto-create-service-principal-portal#required-permissions) to verify that your account can create the identity.
162
+
> If you encounter problems, check the [required permissions](/entra/identity-platform/howto-create-service-principal-portal#permissions-required-for-registering-an-app) to verify that your account can create the identity.
163
163
164
164
1. Open the Microsoft Entra admin center at <https://portal.azure.com/>.
165
165
@@ -187,7 +187,7 @@ For a detailed visual flow about creating applications in Microsoft Entra ID, se
187
187
- **URI**: Enter the URI where the access token is sent.
188
188
189
189
> [!NOTE]
190
-
> You can't create credentials for [native applications](/azure/active-directory/manage-apps/application-proxy-configure-native-client-application), because you can't use native applications for automated applications.
190
+
> You can't create credentials for [native applications](/entra/identity/app-proxy/application-proxy-configure-native-client-application), because you can't use native applications for automated applications.
191
191
192
192

193
193
@@ -391,7 +391,7 @@ If you made the application multi-tenant for **Exchange Online** delegated scena
391
391
-`<client-id>` is the ID of the multi-tenant application.
392
392
- The default scope is used to grant application permissions.
393
393
394
-
For more information about the URL syntax, see [Request the permissions from a directory admin](/azure/active-directory/develop/v2-admin-consent#request-the-permissions-from-a-directory-admin).
394
+
For more information about the URL syntax, see [Request the permissions from a directory admin](/entra/identity-platform/v2-admin-consent#request-the-permissions-from-a-directory-admin).
395
395
396
396
### Step 5: Assign Microsoft Entra roles to the application
397
397
@@ -411,14 +411,14 @@ The supported Microsoft Entra roles are described in the following table:
> <sup>\*</sup> The Global Administrator and Exchange Administrator roles provide the required permissions for any task in Exchange Online PowerShell. For example:
424
424
>
@@ -427,7 +427,7 @@ The supported Microsoft Entra roles are described in the following table:
427
427
>
428
428
> The Security Administrator role does not have the necessary permissions for those same tasks.
429
429
430
-
For general instructions about assigning roles in Microsoft Entra ID, see [View and assign administrator roles in Microsoft Entra ID](/azure/active-directory/roles/manage-roles-portal).
430
+
For general instructions about assigning roles in Microsoft Entra ID, see [Assign Microsoft Entra roles to users](/entra/identity/role-based-access-control/manage-roles-portal).
431
431
432
432
> [!NOTE]
433
433
> The following steps are slightly different for Exchange Online PowerShell vs. Security & Compliance PowerShell. The steps for both environments are shown. To configure roles for both environments, repeat the steps in this section.
@@ -481,7 +481,7 @@ For general instructions about assigning roles in Microsoft Entra ID, see [View
481
481
>
482
482
> This method is supported only when you connect to Exchange Online PowerShell or Security & Compliance PowerShell in [REST API mode](exchange-online-powershell-v2.md#rest-api-connections-in-the-exo-v3-module). Security & Compliance PowerShell supports REST API mode in v3.2.0 or later.
483
483
484
-
For information about creating custom role groups, see [Create role groups in Exchange Online](/exchange/permissions-exo/role-groups#create-role-groups) and [Create Email & collaboration role groups in the Microsoft Defender portal](/microsoft-365/security/office-365-security/mdo-portal-permissions#create-email--collaboration-role-groups-in-the-microsoft-365-defender-portal). The custom role group that you assign to the application can contain any combination of built-in and custom roles.
484
+
For information about creating custom role groups, see [Create role groups in Exchange Online](/exchange/permissions-exo/role-groups#create-role-groups) and [Create Email & collaboration role groups in the Microsoft Defender portal](/microsoft-365/security/office-365-security/mdo-portal-permissions#create-email--collaboration-role-groups-in-the-microsoft-defender-portal). The custom role group that you assign to the application can contain any combination of built-in and custom roles.
485
485
486
486
To assign custom role groups to the application using service principals, do the following steps:
Copy file name to clipboardExpand all lines: exchange/docs-conceptual/connect-exo-powershell-managed-identity.md
+15-15Lines changed: 15 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ description: "Learn about using the Exchange Online PowerShell V3 module and Azu
19
19
20
20
# Use Azure managed identities to connect to Exchange Online PowerShell
21
21
22
-
Using the [Exchange Online PowerShell V3 module](exchange-online-powershell-v2.md#rest-api-connections-in-the-exo-v3-module), you can connect to Exchange Online PowerShell using a user-assigned or system assigned Azure managed identity. For more information about managed identities, see [What are managed identities for Azure resources?](/azure/active-directory/managed-identities-azure-resources/overview).
22
+
Using the [Exchange Online PowerShell V3 module](exchange-online-powershell-v2.md#rest-api-connections-in-the-exo-v3-module), you can connect to Exchange Online PowerShell using a user-assigned or system assigned Azure managed identity. For more information about managed identities, see [What are managed identities for Azure resources?](/entra/identity/managed-identities-azure-resources/overview).
23
23
24
24
Unlike other connection methods using the Exchange Online PowerShell module, you can't run the connection commands in a Windows PowerShell session on your local computer. Instead, you connect in the context of the Azure resource that's associated with the managed identity (for example, an Azure automation account or an Azure Virtual Machine).
25
25
@@ -217,9 +217,9 @@ To create the Automation account with system-assigned managed identity in [Azure
217
217
218
218
For instructions, see the following articles:
219
219
220
-
-[System-assigned managed identity in the Azure portal](/azure/active-directory/managed-identities-azure-resources/qs-configure-portal-windows-vm#system-assigned-managed-identity)
220
+
-[System-assigned managed identity in the Azure portal](/entra/identity/managed-identities-azure-resources/qs-configure-portal-windows-vm#system-assigned-managed-identity)
221
221
222
-
-[System-assigned managed identity in PowerShell](/azure/active-directory/managed-identities-azure-resources/qs-configure-powershell-windows-vm#system-assigned-managed-identity)
222
+
-[System-assigned managed identity in PowerShell](/entra/identity/managed-identities-azure-resources/qs-configure-powershell-windows-vm#system-assigned-managed-identity)
223
223
224
224
### Step 2: Store the system-assigned managed identity in a variable
225
225
@@ -360,14 +360,14 @@ Now that the Office 365 Exchange Online resource is available, return to Step 4.
360
360
361
361
The supported Microsoft Entra roles are described in the following list:
> <sup>\*</sup> The Global Administrator and Exchange Administrator roles provide the required permissions for any task in Exchange Online PowerShell. For example:
373
373
>
@@ -376,7 +376,7 @@ The supported Microsoft Entra roles are described in the following list:
376
376
>
377
377
> The Security Administrator role does not have the necessary permissions for those same tasks.
378
378
379
-
For general instructions about assigning roles in Microsoft Entra ID, see [View and assign administrator roles in Microsoft Entra ID](/azure/active-directory/roles/manage-roles-portal).
379
+
For general instructions about assigning roles in Microsoft Entra ID, see [Assign Microsoft Entra roles to users](/entra/identity/role-based-access-control/manage-roles-portal).
380
380
381
381
1. In Microsoft Entra admin center at <https://portal.azure.com/>, start typing **roles and administrators** in the **Search** box at the top of the page, and then select **Microsoft Entra roles and administrators** from the results in the **Services** section.
382
382
@@ -449,7 +449,7 @@ After you complete the steps, you're ready to [Connect to Exchange Online PowerS
449
449
450
450
If you already have an existing user-assigned managed identity that you're going to use, you can skip to the [next step](#step-2-create-a-resource-with-user-assigned-managed-identity) to create a resource with the user-assigned managed identity.
451
451
452
-
Otherwise, create the user-assigned managed identity in the Azure portal by using the instructions at [Create a user-assigned managed identity](/azure/active-directory/managed-identities-azure-resources/how-manage-user-assigned-managed-identities?pivots=identity-mi-methods-azp#create-a-user-assigned-managed-identity).
452
+
Otherwise, create the user-assigned managed identity in the Azure portal by using the instructions at [Create a user-assigned managed identity](/entra/identity/managed-identities-azure-resources/how-manage-user-assigned-managed-identities?pivots=identity-mi-methods-azp#create-a-user-assigned-managed-identity).
453
453
454
454
To create the user-assigned managed identity in [Azure PowerShell](/powershell/azure/what-is-azure-powershell), do the following steps:
455
455
@@ -547,8 +547,8 @@ To create the Automation account with user-assigned managed identity in [Azure P
547
547
548
548
For instructions, see the following articles:
549
549
550
-
-[User-assigned managed identity in the Azure portal](/azure/active-directory/managed-identities-azure-resources/qs-configure-portal-windows-vm#user-assigned-managed-identity)
551
-
-[User-assigned managed identity in PowerShell](/azure/active-directory/managed-identities-azure-resources/qs-configure-powershell-windows-vm#user-assigned-managed-identity)
550
+
-[User-assigned managed identity in the Azure portal](/entra/identity/managed-identities-azure-resources/qs-configure-portal-windows-vm#user-assigned-managed-identity)
551
+
-[User-assigned managed identity in PowerShell](/entra/identity/managed-identities-azure-resources/qs-configure-powershell-windows-vm#user-assigned-managed-identity)
552
552
553
553
### Step 3: Store the user-assigned managed identity in a variable
Copy file name to clipboardExpand all lines: exchange/exchange-ps/exchange/Add-VivaModuleFeaturePolicy.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,7 +47,7 @@ This cmdlet requires the .NET Framework 4.7.2 or later.
47
47
48
48
Currently, you need to be a member of the Global administrators role to run this cmdlet.
49
49
50
-
To learn more about administrator role permissions in Microsoft Entra ID, see [Role template IDs](https://learn.microsoft.com/azure/active-directory/roles/permissions-reference#role-template-ids).
50
+
To learn more about administrator role permissions in Microsoft Entra ID, see [Role template IDs](https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference#role-template-ids).
51
51
52
52
## EXAMPLES
53
53
@@ -301,4 +301,4 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable
301
301
302
302
[About the Exchange Online PowerShell module](https://learn.microsoft.com/powershell/exchange/exchange-online-powershell-v2)
Copy file name to clipboardExpand all lines: exchange/exchange-ps/exchange/Get-DefaultTenantBriefingConfig.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,7 @@ To run this cmdlet, you need to be a member of one of the following directory ro
38
38
- Exchange Administrator
39
39
- Insights Administrator
40
40
41
-
For more information, see [Microsoft Entra built-in roles](https://learn.microsoft.com/azure/active-directory/roles/permissions-reference).
41
+
For more information, see [Microsoft Entra built-in roles](https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference).
Copy file name to clipboardExpand all lines: exchange/exchange-ps/exchange/Get-DefaultTenantMyAnalyticsFeatureConfig.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ To run this cmdlet, you need to be a member of one of the following directory ro
34
34
- Exchange Administrator
35
35
- Insights Administrator
36
36
37
-
For more information, see [Microsoft Entra built-in roles](https://learn.microsoft.com/azure/active-directory/roles/permissions-reference).
37
+
For more information, see [Microsoft Entra built-in roles](https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference).
Copy file name to clipboardExpand all lines: exchange/exchange-ps/exchange/Get-MyAnalyticsFeatureConfig.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,7 +35,7 @@ This cmdlet requires the .NET Framework 4.7.2 or later. To run this cmdlet, you
35
35
- Exchange Administrator
36
36
- Insights Administrator
37
37
38
-
To learn more about administrator role permissions in Microsoft Entra ID, see [Role template IDs](https://learn.microsoft.com/azure/active-directory/roles/permissions-reference#role-template-ids).
38
+
To learn more about administrator role permissions in Microsoft Entra ID, see [Role template IDs](https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference#role-template-ids).
Service principals exist in Microsoft Entra ID to define what apps can do, who can access the apps, and what resources the apps can access. In Exchange Online, service principals are references to the service principals in Microsoft Entra ID. To assign Exchange Online role-based access control (RBAC) roles to service principals in Microsoft Entra ID, you use the service principal references in Exchange Online. The **\*-ServicePrincipal** cmdlets in Exchange Online PowerShell let you view, create, and remove these service principal references.
31
31
32
-
For more information, see [Application and service principal objects in Microsoft Entra ID](https://learn.microsoft.com/azure/active-directory/develop/app-objects-and-service-principals).
32
+
For more information, see [Application and service principal objects in Microsoft Entra ID](https://learn.microsoft.com/entra/identity-platform/app-objects-and-service-principals).
33
33
34
34
You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
Copy file name to clipboardExpand all lines: exchange/exchange-ps/exchange/Get-UserBriefingConfig.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,7 +32,7 @@ This cmdlet requires the .NET Framework 4.7.2 or later. To run this cmdlet, you
32
32
- Exchange Administrator
33
33
- Insights Administrator
34
34
35
-
To learn more about administrator role permissions in Microsoft Entra ID, see [Role template IDs](https://learn.microsoft.com/azure/active-directory/roles/permissions-reference#role-template-ids).
35
+
To learn more about administrator role permissions in Microsoft Entra ID, see [Role template IDs](https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference#role-template-ids).
Copy file name to clipboardExpand all lines: exchange/exchange-ps/exchange/Get-VivaInsightsSettings.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,7 @@ This cmdlet requires the .NET Framework 4.7.2 or later. To run this cmdlet, you
36
36
- Exchange Administrator
37
37
- Teams Administrator
38
38
39
-
To learn more about administrator role permissions in Microsoft Entra ID, see [Role template IDs](https://learn.microsoft.com/azure/active-directory/roles/permissions-reference#role-template-ids).
39
+
To learn more about administrator role permissions in Microsoft Entra ID, see [Role template IDs](https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference#role-template-ids).
0 commit comments