Merge pull request #407 from chrisda/patch-3

Update how-to-control-access-to-ews-in-exchange.md

Author: lindalu-MSFT

docs/exchange-web-services/how-to-control-access-to-ews-in-exchange.md

@@ -1,11 +1,11 @@
 ---
 title: "Control access to EWS in Exchange"
 manager: sethgros
-ms.date: 09/17/2015
+ms.date: 04/07/2025
 ms.audience: Developer
 ms.assetid: 61e29e54-e3e5-404a-84c0-93b61a25ca58
 description: "Find out how to control access to EWS for users, applications, or the entire organization."
-localization_priority: Priority
+ms.localizationpriority: high
 ---
 
 # Control access to EWS in Exchange
@@ -19,10 +19,10 @@ Whether you are using the EWS Managed API, or EWS directly, in your application,
 
 You can use the following Exchange Management Shell cmdlets to view the current access configuration and set EWS access controls:
 
-- [Get-CASMailbox](https://technet.microsoft.com/library/bb124754.aspx) - Shows you what parameters are set for a particular mailbox.   
-- [Set-CASMailbox](https://technet.microsoft.com/library/bb125264.aspx) - Sets parameters for a particular mailbox.    
-- [Get-OrganizationConfig](https://technet.microsoft.com/library/aa997571.aspx) - Shows you the parameters for the entire organization.    
-- [Set-OrganizationConfig](https://technet.microsoft.com/library/aa997443.aspx) - Sets the parameters for the entire organization. 
+- [Get-CASMailbox](/powershell/module/exchange/get-casmailbox) - Shows you what parameters are set for a particular mailbox.   
+- [Set-CASMailbox](/powershell/module/exchange/set-casmailbox) - Sets parameters for a particular mailbox.    
+- [Get-OrganizationConfig](/powershell/module/exchange/get-organizationconfig) - Shows you the parameters for the entire organization.    
+- [Set-OrganizationConfig](/powershell/module/exchange/set-organizationconfig) - Sets the parameters for the entire organization. 
 
 <a name="bk_Examples"> </a>
 
@@ -38,7 +38,7 @@ Let's take a look at a few scenarios that show you how you can control access to
 |Allow a list of client applications to use EWS. | `Set-OrganizationConfig -EwsApplicationAccessPolicy:EnforceAllowList -EwsAllowList:"OWA/*"`<br/><br/>This allows specific applications to use EWS. In this example, any application that has a user agent string that starts with "OWA/" is allowed access. |
 |Allow all client applications to use EWS except those that are specifically blocked. | `Set-OrganizationConfig -EwsApplicationAccessPolicy:EnforceBlockList -EwsBlockList:"OWA/*"`<br/> <br/>This example only blocks applications from using EWS that have a user agent string that starts with "OWA/". |
 |Allow all client applications to use EWS. | `Set-OrganizationConfig -EwsApplicationAccessPolicy:EnforceBlockList` <br/><br/> Because no BlockList is specified, all applications can use EWS. |
-|Block the entire organization from using EWS. | `Set-OrganizationConfig -EwsEnabled:$false` |
+|Block the entire organization from using EWS. | `Set-OrganizationConfig -EwsEnabled:$false` <br/><br/> **Important**: Disabling EWS in the organization also disables per-user EWS overrides. |
 |Allow the entire organization to use EWS. | `Set-OrganizationConfig -EwsEnabled:$true`|
 |Block an individual mailbox from using EWS. | `Set-CASMailbox -Identity [email protected] -EwsEnabled:$false`|
 |Allow an individual mailbox to use EWS. | `Set-CASMailbox -Identity [email protected] -EwsEnabled:$true`|
@@ -47,5 +47,5 @@ Let's take a look at a few scenarios that show you how you can control access to
 
 - [Setting up your EWS application](setting-up-your-ews-application.md)    
 - [Controlling client application access to EWS in Exchange](controlling-client-application-access-to-ews-in-exchange.md)   
-- [Exchange Server PowerShell (Exchange Management Shell)](/powershell/exchange/exchange-server/exchange-management-shell?view=exchange-ps) 
-- [Windows PowerShell](https://msdn.microsoft.com/library/dd835506%28v=vs.85%29.aspx)
+- [Exchange Server PowerShell (Exchange Management Shell)](/powershell/exchange/exchange-management-shell) 
+- [Windows PowerShell](/powershell/scripting/overview)