Merge pull request MicrosoftDocs#4250 from MicrosoftDocs/chrisda

Fixed remaining broken technet and fwlinks in Ex cmdlets

Author: chrisda

exchange/exchange-ps/exchange/advanced-threat-protection/Disable-AntiPhishRule.md

@@ -108,4 +108,4 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable
 
 ## RELATED LINKS
 
-[Online version](https://technet.microsoft.com/library/679dceee-3fa7-4ef4-8176-46cf7e6d6d7f.aspx)
+[Online Version](https://technet.microsoft.com/library/679dceee-3fa7-4ef4-8176-46cf7e6d6d7f.aspx)

exchange/exchange-ps/exchange/advanced-threat-protection/Enable-AntiPhishRule.md

@@ -108,4 +108,4 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable
 
 ## RELATED LINKS
 
-[Online version](https://technet.microsoft.com/library/5579e1ca-ed86-4bd6-8043-23bd405ccb1a.aspx)
+[Online Version](https://technet.microsoft.com/library/5579e1ca-ed86-4bd6-8043-23bd405ccb1a.aspx)

exchange/exchange-ps/exchange/advanced-threat-protection/Get-AntiPhishPolicy.md

@@ -126,4 +126,4 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable
 
 ## RELATED LINKS
 
-[Online version](https://technet.microsoft.com/library/b4aa4010-5c31-4a84-8465-9c9507f38715.aspx)
+[Online Version](https://technet.microsoft.com/library/b4aa4010-5c31-4a84-8465-9c9507f38715.aspx)

exchange/exchange-ps/exchange/advanced-threat-protection/Get-AntiPhishRule.md

@@ -96,4 +96,4 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable
 
 ## RELATED LINKS
 
-[Online version](https://technet.microsoft.com/library/c546e813-d7d2-45d6-bb35-839d16e1f7ee.aspx)
+[Online Version](https://technet.microsoft.com/library/c546e813-d7d2-45d6-bb35-839d16e1f7ee.aspx)

exchange/exchange-ps/exchange/advanced-threat-protection/Get-AtpPolicyForO365.md

@@ -25,9 +25,9 @@ Get-AtpPolicyForO365 [[-Identity] <AtpPolicyForO365IdParameter>] [<CommonParamet
 ```
 
 ## DESCRIPTION
-Safe Links is a feature in Advanced Threat Protection that checks links in email messages to see if they lead to malicious web sites. For more information, see ATP safe links in Office 365 (https://go.microsoft.com/fwlink/p/?linkid=846016).
+Safe Links is a feature in Advanced Threat Protection that checks links in email messages to see if they lead to malicious web sites. For more information, see [Office 365 ATP Safe Links](https://docs.microsoft.com/microsoft-365/security/office-365-security/atp-safe-links).
 
-ATP can also protect files in SharePoint Online, OneDrive for Business and Microsoft Teams by preventing users from opening and downloading files that are identified as malicious. For more information, see Office 365 Advanced Threat Protection for SharePoint, OneDrive and Teams (https://go.microsoft.com/fwlink/p/?linkid=857638).
+ATP can also protect files in SharePoint Online, OneDrive for Business and Microsoft Teams by preventing users from opening and downloading files that are identified as malicious. For more information, see [Office 365 ATP for SharePoint, OneDrive, and Microsoft Teams](https://go.microsoft.com/fwlink/p/?linkid=857638).
 
 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://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions).
 

exchange/exchange-ps/exchange/advanced-threat-protection/Get-PhishFilterPolicy.md

@@ -45,7 +45,7 @@ The Get-PhishFilterPolicy cmdlet returns the following information:
 
 - Spoof Type: Indicates whether the domain is internal to your organization or external.
 
-For more information about spoof intelligence, see Learn more about spoof intelligence (https://go.microsoft.com/fwlink/p/?linkid=869584).
+For more information about spoof intelligence, see [Learn more about spoof intelligence](https://go.microsoft.com/fwlink/p/?linkid=869584).
 
 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://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions).
 

exchange/exchange-ps/exchange/advanced-threat-protection/New-AntiPhishRule.md

@@ -354,4 +354,4 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable
 
 ## RELATED LINKS
 
-[Online version](https://technet.microsoft.com/library/cee3f810-9895-420f-b22f-f8937d8b60df.aspx)
+[Online Version](https://technet.microsoft.com/library/cee3f810-9895-420f-b22f-f8937d8b60df.aspx)

exchange/exchange-ps/exchange/advanced-threat-protection/Remove-AntiPhishPolicy.md

@@ -124,4 +124,4 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable
 
 ## RELATED LINKS
 
-[Online version](https://technet.microsoft.com/library/5d497eed-c33c-4280-a5fe-945546ab1492.aspx)
+[Online Version](https://technet.microsoft.com/library/5d497eed-c33c-4280-a5fe-945546ab1492.aspx)

exchange/exchange-ps/exchange/advanced-threat-protection/Remove-AntiPhishRule.md

@@ -108,4 +108,4 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable
 
 ## RELATED LINKS
 
-[Online version](https://technet.microsoft.com/library/c7ca44b1-c3a5-4699-aaf8-c1b07f85d4fa.aspx)
+[Online Version](https://technet.microsoft.com/library/c7ca44b1-c3a5-4699-aaf8-c1b07f85d4fa.aspx)

exchange/exchange-ps/exchange/advanced-threat-protection/Set-AntiPhishRule.md

@@ -346,4 +346,4 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable
 
 ## RELATED LINKS
 
-[Online version](https://technet.microsoft.com/library/b9bbb572-f8d9-4a3c-9471-19b91a07acba.aspx)
+[Online Version](https://technet.microsoft.com/library/b9bbb572-f8d9-4a3c-9471-19b91a07acba.aspx)

exchange/exchange-ps/exchange/advanced-threat-protection/Set-AtpPolicyForO365.md

@@ -36,9 +36,9 @@ Set-AtpPolicyForO365 [[-Identity] <AtpPolicyForO365IdParameter>]
 ```
 
 ## DESCRIPTION
-Safe Links is a feature in Advanced Threat Protection that checks links in email messages to see if they lead to malicious web sites. For more information, see ATP safe links in Office 365 (https://go.microsoft.com/fwlink/p/?linkid=857638).
+Safe Links is a feature in Advanced Threat Protection that checks links in email messages to see if they lead to malicious web sites. For more information, see [Office 365 ATP Safe Links](https://docs.microsoft.com/microsoft-365/security/office-365-security/atp-safe-links).
 
-ATP can also protect files in SharePoint Online, OneDrive for Business and Microsoft Teams by preventing users from opening and downloading files that are identified as malicious. For more information, see Office 365 Advanced Threat Protection for SharePoint, OneDrive and Teams (https://go.microsoft.com/fwlink/p/?linkid=857638).
+ATP can also protect files in SharePoint Online, OneDrive for Business and Microsoft Teams by preventing users from opening and downloading files that are identified as malicious. For more information, see [Office 365 ATP for SharePoint, OneDrive, and Microsoft Teams](https://go.microsoft.com/fwlink/p/?linkid=857638).
 
 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://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions).
 

exchange/exchange-ps/exchange/advanced-threat-protection/Set-PhishFilterPolicy.md

@@ -27,7 +27,7 @@ Set-PhishFilterPolicy [-Identity] <HostedConnectionFilterPolicyIdParameter> -Spo
 
 ## DESCRIPTION
 
-For more information about spoof intelligence, see Learn more about spoof intelligence (https://go.microsoft.com/fwlink/p/?linkid=869584).
+For more information about spoof intelligence, see [Learn more about spoof intelligence](https://go.microsoft.com/fwlink/p/?linkid=869584).
 
 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://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions).
 

exchange/exchange-ps/exchange/antispam-antimalware/Get-MailboxJunkEmailConfiguration.md

@@ -32,7 +32,7 @@ The junk email settings on the mailbox are:
 
 - Configure the safelist collection: The safelist collection is the Safe Senders list, the Safe Recipients list, and the Blocked Senders list. Users can configure the safelist collection on their own mailbox by using Microsoft Outlook or Outlook on the web.
 
-Administrators can enable or disable the junk email rule, and configure the safelist collection on a mailbox by using the Set-MailboxJunkEmailConfiguration cmdlet. For more information, see Configure Exchange antispam settings on mailboxes (https://technet.microsoft.com/library/bb123559.aspx).
+Administrators can enable or disable the junk email rule, and configure the safelist collection on a mailbox by using the Set-MailboxJunkEmailConfiguration cmdlet. For more information, see [Configure Exchange antispam settings on mailboxes](https://docs.microsoft.com/Exchange/antispam-and-antimalware/antispam-protection/configure-antispam-settings).
 
 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://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions).
 

exchange/exchange-ps/exchange/antispam-antimalware/Set-MailboxJunkEmailConfiguration.md

@@ -37,7 +37,7 @@ This cmdlet controls the following junk email settings on the mailbox:
 
 - Configure the safelist collection: The safelist collection is the Safe Senders list, the Safe Recipients list, and the Blocked Senders list. Users can configure the safelist collection on their own mailbox by using Microsoft Outlook or Outlook on the web.
 
-For more information, see Configure Exchange antispam settings on mailboxes (https://technet.microsoft.com/library/bb123559.aspx).
+For more information, see [Configure Exchange antispam settings on mailboxes](https://docs.microsoft.com/Exchange/antispam-and-antimalware/antispam-protection/configure-antispam-settings).
 
 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://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions).
 
@@ -194,7 +194,7 @@ You can view the status of the junk email rule by running either of the followin
 
 You use the JunkEmailEnabled parameter on the Set-OwaMailboxPolicy or Set-OwaVirtualDirectory cmdlets to control the availability of the junk email settings in Outlook on the web.
 
-The state of the junk email rule on the mailbox doesn't affect the client-side junk email settings that are available in the Outlook Junk Email Filter. Even when the junk email rule is disabled in the mailbox, Outlook can still move messages to the Junk Email folder. For example, if Outlook determines the message is spam, or the sender is defined in the Blocked Senders list, Outlook can move the message to the Junk Email folder. For more information, see Configure junk email settings in Outlook 2013 (https://go.microsoft.com/fwlink/p/?LinkID=797542).
+The state of the junk email rule on the mailbox doesn't affect the client-side junk email settings that are available in the Outlook Junk Email Filter. Even when the junk email rule is disabled in the mailbox, Outlook can still move messages to the Junk Email folder. For example, if Outlook determines the message is spam, or the sender is defined in the Blocked Senders list, Outlook can move the message to the Junk Email folder. For more information, see [Use Junk Email Filters to control which messages you see](https://go.microsoft.com/fwlink/p/?LinkID=797542).
 
 ```yaml
 Type: $true | $false
@@ -263,7 +263,7 @@ Notes:
 
 - You can't directly modify the Safe Recipients list by using this cmdlet. You use this parameter to modify the Safe Senders list, and the email addresses and domains are synchronized to the Safe Recipients list.
 
-- Safe domains aren't recognized in Exchange Online and Exchange Online Protection. For more information, see Domains on the Outlook Safe Senders list aren't recognized by Exchange Online or Exchange Online Protection (https://go.microsoft.com/fwlink/p/?linkid=859868).
+- Safe domains aren't recognized in Exchange Online and Exchange Online Protection. For more information, see [KB3019657](https://go.microsoft.com/fwlink/p/?linkid=859868).
 
 ```yaml
 Type: MultiValuedProperty

exchange/exchange-ps/exchange/client-access-servers/Get-ClientAccessArray.md

@@ -32,7 +32,7 @@ Changes in the Exchange server architecture that were introduced in Exchange Ser
 
 - Outlook clients can't use RPC over TCP to access mailboxes on Exchange Server 2013 or later versions and RPC Client Access arrays only work with RPC over TCP.
 
-- Because the Client Access server role is now a stateless proxy, you use different and less complex methods to configure load balancing and high availability for internal and external client connections. For more information, see Load balancing in Exchange 2016 (https://technet.microsoft.com/library/jj898588.aspx).
+- Because the Client Access server role is now a stateless proxy, you use different and less complex methods to configure load balancing and high availability for internal and external client connections. For more information, see [Load balancing in Exchange Server](https://docs.microsoft.com/Exchange/architecture/client-access/load-balancing).
 
 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://docs.microsoft.com/powershell/exchange/exchange-server/find-exchange-cmdlet-permissions).
 

exchange/exchange-ps/exchange/client-access-servers/New-WebServicesVirtualDirectory.md

@@ -325,7 +325,7 @@ Accept wildcard characters: False
 ```
 
 ### -MRSProxyEnabled
-The MRSProxyEnabled parameter specifies whether to enable MRSProxy for the Mailbox server. MRSProxy is a service that runs on Mailbox servers in a remote forest and helps to proxy a mailbox move. For more information, see Mailbox moves (https://technet.microsoft.com/library/jj150543.aspx).
+The MRSProxyEnabled parameter specifies whether to enable MRSProxy for the Mailbox server. MRSProxy is a service that runs on Mailbox servers in a remote forest and helps to proxy a mailbox move. For more information, see [Mailbox moves in Exchange Server](https://docs.microsoft.com/Exchange/recipients/mailbox-moves).
 
 ```yaml
 Type: $true | $false

exchange/exchange-ps/exchange/client-access-servers/Set-EcpVirtualDirectory.md

@@ -109,7 +109,7 @@ Accept wildcard characters: False
 ```
 
 ### -AdminEnabled
-The AdminEnabled parameter specifies that the EAC isn't able to be accessed through the Internet. For more information, see Turn off access to the Exchange admin center (https://technet.microsoft.com/library/jj218639.aspx). This parameter accepts $true or $false.
+The AdminEnabled parameter specifies that the EAC isn't able to be accessed through the Internet. For more information, see [Turn off access to the Exchange admin center](https://docs.microsoft.com/Exchange/architecture/client-access/disable-exchange-admin-center-acces). This parameter accepts $true or $false.
 
 ```yaml
 Type: $true | $false

exchange/exchange-ps/exchange/client-access-servers/Set-OwaVirtualDirectory.md

@@ -161,7 +161,7 @@ Before you run the Set-OwaVirtualDirectory cmdlet, consider the following items:
 
 - You can run the Set-OwaVirtualDirectory cmdlet on any server that has the Exchange Server administration tools installed.
 
-- Several parameters for the Set-OwaVirtualDirectory cmdlet can contain more than one value. These are known as multivalued properties. Make sure that you modify multivalued properties correctly. For information, see Modifying multivalued properties (https://technet.microsoft.com/library/bb684908.aspx).
+- Several parameters for the Set-OwaVirtualDirectory cmdlet can contain more than one value. These are known as multivalued properties. Make sure that you modify multivalued properties correctly. For information, see [Modifying multivalued properties](https://docs.microsoft.com/exchange/modifying-multivalued-properties-exchange-2013-help).
 
 - Many of the Outlook on the web virtual directory settings require you to restart IIS (Stop-Service WAS -Force and Start-Service W3SVC) before the change takes effect. For example, when you enable or disable forms-based authentication, or when you enable or disable the Private computer option on the sign-in page.
 
@@ -2192,7 +2192,7 @@ The SMimeEnabled parameter specifies whether users can download the S/MIME contr
 
 - $false: Users can't read or compose messages in Outlook Web App that are opaque-signed or encrypted by using S/MIME. Messages that are clear-signed can be read but not composed, and their signatures aren't validated.
 
-**Note**: In Exchange 2013 or later, use the Get-SmimeConfig and Set-SmimeConfig cmdlets to configure the S/MIME settings in Outlook on the web. For more information, see {S/MIME for message signing and encryption](https://technet.microsoft.com/library/dn626158.aspx).
+**Note**: In Exchange 2013 or later, use the Get-SmimeConfig and Set-SmimeConfig cmdlets to configure the S/MIME settings in Outlook on the web. For more information, see [S/MIME for message signing and encryption](https://docs.microsoft.com/Exchange/policy-and-compliance/smime).
 
 ```yaml
 Type: $true | $false

exchange/exchange-ps/exchange/client-access/Set-MailboxRegionalConfiguration.md

@@ -125,7 +125,7 @@ The DateFormat parameter specifies the date format based on the current or speci
 
 - dd-MMM-yy
 
-For more information about the date format strings, see Standard Date and Time Format Strings (https://go.microsoft.com/fwlink/p/?LinkId=784852).
+For more information about the date format strings, see [Standard Date and Time Format Strings](https://go.microsoft.com/fwlink/p/?LinkId=784852).
 
 ```yaml
 Type: String
@@ -199,7 +199,7 @@ The TimeFormat parameter specifies the time format based on the current or speci
 
 - HH:mm
 
-For more information about the time format strings, see Standard Date and Time Format Strings (https://go.microsoft.com/fwlink/p/?LinkId=784852).
+For more information about the time format strings, see [Standard Date and Time Format Strings](https://go.microsoft.com/fwlink/p/?LinkId=784852).
 
 ```yaml
 Type: String

exchange/exchange-ps/exchange/client-access/Set-OwaMailboxPolicy.md

@@ -1768,7 +1768,7 @@ The SMimeEnabled parameter specifies whether users can download the S/MIME contr
 
 - $false: Users can't read or compose messages in Outlook Web App that are opaque-signed or encrypted by using S/MIME. Messages that are clear-signed can be read but not composed, and their signatures aren't validated.
 
-**Note**: In Exchange 2013 or later, use the Get-SmimeConfig and Set-SmimeConfig cmdlets to configure the S/MIME settings in Outlook on the web. For more information, see {S/MIME for message signing and encryption](https://technet.microsoft.com/library/dn626158.aspx).
+**Note**: In Exchange 2013 or later, use the Get-SmimeConfig and Set-SmimeConfig cmdlets to configure the S/MIME settings in Outlook on the web. For more information, see [S/MIME for message signing and encryption](https://docs.microsoft.com/Exchange/policy-and-compliance/smime).
 
 ```yaml
 Type: $true | $false