Skip to content

Commit 9f6cff0

Browse files
authored
Merge pull request MicrosoftDocs#7215 from MicrosoftDocs/chrisda
Chrisda to Master
2 parents cd4c323 + f33907b commit 9f6cff0

File tree

4 files changed

+6
-6
lines changed

4 files changed

+6
-6
lines changed

exchange/docs-conceptual/app-only-auth-powershell-v2.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ description: "Learn about using the Exchange Online V2 module in scripts and oth
1919
# App-only authentication for unattended scripts in the EXO V2 module
2020

2121
> [!NOTE]
22-
> The required `2.0.3` version of the EXO V2 module for this feature is now Generally Available. For instructions on how to install or update to this version of the module, see [Install and maintain the EXO V2 module](exchange-online-powershell-v2.md#install-and-maintain-the-exo-v2-module).
22+
> The features and procedures described in this article require version 2.0.3 or later of the EXO V2 module. For instructions on how to install or update to this version of the module, see [Install and maintain the EXO V2 module](exchange-online-powershell-v2.md#install-and-maintain-the-exo-v2-module).
2323
2424
Auditing and reporting scenarios in Exchange Online often involve scripts that run unattended. In most cases, these unattended scripts access Exchange Online PowerShell using Basic authentication (a username and password). Even when the connection to Exchange Online PowerShell uses modern authentication, the credentials are stored in a local file or a secret vault that's accessed at run-time.
2525

@@ -134,7 +134,8 @@ For a detailed visual flow about creating applications in Azure AD, see <https:/
134134

135135
## Step 2: Assign API permissions to the application
136136

137-
You need to assign the API permission `Exchange.ManageAsApp` so the application can manage Exchange Online. API permissions are required because they have consent flow enabled, which allows auditing (directory roles don't have consent flow).
137+
> [!NOTE]
138+
> The procedures in this section replace any default permissions that were automatically configured for the new app. The app doesn't need the default permissions that were replaced.
138139
139140
1. On the app page under **Management**, select **Manifest**.
140141

exchange/exchange-ps/exchange/Add-UnifiedGroupLinks.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -100,6 +100,7 @@ Accept wildcard characters: False
100100
### -LinkType
101101
The LinkType parameter specifies the Microsoft 365 Group property that you want to modify. Valid values are:
102102

103+
- Aggregators
103104
- Members
104105
- Owners
105106
- Subscribers

exchange/exchange-ps/exchange/Get-UnifiedGroupLinks.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -70,11 +70,10 @@ Accept wildcard characters: False
7070
### -LinkType
7171
The LinkType parameter specifies the Microsoft 365 Group property that you want to view. Valid values are:
7272
73+
- Aggregators
7374
- Members
7475
- Owners
7576
- Subscribers
76-
- Aggregators
77-
- EventSubscribers
7877
7978
```yaml
8079
Type: LinkType

exchange/exchange-ps/exchange/Remove-UnifiedGroupLinks.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -98,11 +98,10 @@ Accept wildcard characters: False
9898
### -LinkType
9999
The LinkType parameter specifies the Microsoft 365 Group property that you want to modify. Valid values are:
100100

101+
- Aggregators
101102
- Members
102103
- Owners
103104
- Subscribers
104-
- Aggregators
105-
- EventSubscribers
106105

107106
```yaml
108107
Type: LinkType

0 commit comments

Comments
 (0)