diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OrganizationConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-OrganizationConfig.md index 4e72d05cfd..81d37f2d7f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-OrganizationConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-OrganizationConfig.md @@ -93,6 +93,7 @@ Set-OrganizationConfig -ShortenEventScopeDefault [-EwsAllowList ] [-EwsAllowMacOutlook ] [-EwsAllowOutlook ] + [-EwsAllowedAppIDs ] [-EwsApplicationAccessPolicy ] [-EwsBlockList ] [-EwsEnabled ] @@ -418,6 +419,7 @@ Set-OrganizationConfig [-DelayedDelicensingEnabled ] [-EndUserMailNotif [-EwsAllowList ] [-EwsAllowMacOutlook ] [-EwsAllowOutlook ] + [-EwsAllowedAppIDs ] [-EwsApplicationAccessPolicy ] [-EwsBlockList ] [-EwsEnabled ] @@ -595,6 +597,15 @@ Set-OrganizationConfig -VisibleMeetingUpdateProperties "Location,Subject,Body,Al In Exchange Online, this example results in meeting updates being auto-processed (meeting update messages aren't visible in attendee Inbox folders) except any changes to meeting location, subject and body as well as any property changes within 15 minutes of the meeting start time. +### Example 7 +```powershell +Set-OrganizationConfig -EwsEnabled $true -EwsAllowedAppIDs"aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee,11111111-2222-3333-4444-555555555555" +``` + +This example restricts EWS access to only the two specified Entra applications. All other applications are blocked from accessing EWS. + +**Note**: To remove the application ID restriction on EWS access, use the value `$null`. + ## PARAMETERS ### -ShortenEventScopeDefault @@ -2555,6 +2566,36 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -EwsAllowedAppIDs + +> Applicable: Exchange Online + +This parameter is available only in the cloud-based service. + +The EwsAllowedAppIDs parameter specifies the Azure AD applications that are allowed to access Exchange Web Services (EWS) when the EwsEnabled parameter on this cmdlet is also set to the value $true. Unspecified applications are blocked from accessing EWS. You identify each application by its Azure AD application ID (GUID). + +- When EwsEnabled is $true, only applications specified by this parameter can access EWS. +- When EwsEnabled is $false, all EWS access is blocked regardless of this parameter. +- When EwsEnabled is blank ($null; not configured), this parameter has no effect. + +To specify multiple values, use a comma-separated list of GUIDs: `"AppId1,AppId2,...AppIdN"`. + +To remove all allowed app IDs and stop restricting access by app ID, use the value `$null` for this parameter. + +**Note**: This parameter applies only to direct EWS (SOAP) connections. It doesn't affect requests from the Microsoft Graph API or the REST endpoint. + +```yaml +Type: String +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -EwsApplicationAccessPolicy > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online