Fix links

Author: sethmanheim

azure-stack/operator/azure-stack-integrate-endpoints.md

@@ -87,7 +87,7 @@ SSL traffic interception is [not supported](azure-stack-firewall.md#ssl-intercep
 |**LDAP SSL**<br>Allows Azure Stack Hub to communicate encrypted with Microsoft Active Directory on-premises.|Active Directory Forest provided for Graph integration|TCP 636|Public VIP - /27|Required when Azure Stack Hub is deployed using AD FS.|
 |**LDAP GC**<br>Allows Azure Stack Hub to communicate with Microsoft Active Global Catalog Servers.|Active Directory Forest provided for Graph integration|TCP 3268|Public VIP - /27|Required when Azure Stack Hub is deployed using AD FS.|
 |**LDAP GC SSL**<br>Allows Azure Stack Hub to communicate encrypted with Microsoft Active Directory Global Catalog Servers.|Active Directory Forest provided for Graph integration|TCP 3269|Public VIP - /27|Required when Azure Stack Hub is deployed using AD FS.|
-|**AD FS**<br>Allows Azure Stack Hub to communicate with on-premise AD FS.|AD FS metadata endpoint provided for AD FS integration|TCP 443|Public VIP - /27|Optional. The AD FS claims provider trust can be created using a [metadata file](azure-stack-integrate-identity.md#setting-up-ad-fs-integration-by-providing-federation-metadata-file).|
+|**AD FS**<br>Allows Azure Stack Hub to communicate with on-premise AD FS.|AD FS metadata endpoint provided for AD FS integration|TCP 443|Public VIP - /27|Optional. The AD FS claims provider trust can be created using a [metadata file](azure-stack-integrate-identity.md#set-up-ad-fs-integration-by-providing-federation-metadata-file).|
 |**Diagnostic log collection**<br>Allows Azure Stack Hub to send logs either proactively or manually by an operator to Microsoft support.|`https://*.blob.core.windows.net`<br>`https://azsdiagprdlocalwestus02.blob.core.windows.net`<br>`https://azsdiagprdwestusfrontend.westus.cloudapp.azure.com`<br>`https://azsdiagprdwestusfrontend.westus.cloudapp.azure.com` | HTTPS 443 | Public VIP - /27 |Not required. You can [save logs locally](diagnostic-log-collection.md#save-logs-locally).|
 |**Remote support**<br>Allows Microsoft support professionals to solve support case faster by permitting access to the device remotely to performing limited troubleshooting and repair operations. | `https://edgesupprd.trafficmanager.net`<br>`https://edgesupprdwestusfrontend.westus2.cloudapp.azure.com`<br>`https://edgesupprdwesteufrontend.westeurope.cloudapp.azure.com`<br>`https://edgesupprdeastusfrontend.eastus.cloudapp.azure.com`<br>`https://edgesupprdwestcufrontend.westcentralus.cloudapp.azure.com`<br>`https://edgesupprdasiasefrontend.southeastasia.cloudapp.azure.com`<br>`*.servicebus.windows.net` | HTTPS 443 | Public VIP - /27 | Not required. |
 |**Telemetry**<br>Allows Azure Stack Hub to send telemetry data to Microsoft.|`https://settings-win.data.microsoft.com`<br>`https://login.live.com`<br>`*.events.data.microsoft.com`<br>Beginning with version 2108, the following endpoints are also required:<br>`https://*.blob.core.windows.net/`<br>`https://azsdiagprdwestusfrontend.westus.cloudapp.azure.com/` | HTTPS 443 | Public VIP - /27 | Required when Azure Stack Hub telemetry is enabled. |

azure-stack/operator/relnotearchive/release-notes.md

@@ -3617,7 +3617,7 @@ This update includes the following improvements for Azure Stack.
 - Update to this version no longer resets the default owner of the default provider subscription to the built-in **CloudAdmin** user when deployed with AD FS.
 
 <!-- 2360715 |  ASDK, IS -->  
-- When you set up datacenter integration, you no longer access the AD FS metadata file from an Azure file share. For more information, see [Setting up AD FS integration by providing federation metadata file](../azure-stack-integrate-identity.md#setting-up-ad-fs-integration-by-providing-federation-metadata-file). 
+- When you set up datacenter integration, you no longer access the AD FS metadata file from an Azure file share. For more information, see [Setting up AD FS integration by providing federation metadata file](../azure-stack-integrate-identity.md#set-up-ad-fs-integration-by-providing-federation-metadata-file). 
 
 <!-- 2388980 | ASDK, IS --> 
 - We fixed an issue that prevented users from assigned an existing Public IP Address that had been previously assigned to a Network Interface or Load Balancer to a new Network Interface or Load Balancer.  

azure-stack/ruggedized/operator/azure-stack-integrate-endpoints-tzl.md

@@ -91,7 +91,7 @@ SSL traffic interception is [not supported](../../operator/azure-stack-firewall.
 |**LDAP SSL**<br>Allows Azure Stack Hub to communicate encrypted with Microsoft Active Directory on-premises.|Active Directory Forest provided for Graph integration|TCP 636|Public VIP - /27|Required when Azure Stack Hub is deployed using AD FS.|
 |**LDAP GC**<br>Allows Azure Stack Hub to communicate with Microsoft Active Global Catalog Servers.|Active Directory Forest provided for Graph integration|TCP 3268|Public VIP - /27|Required when Azure Stack Hub is deployed using AD FS.|
 |**LDAP GC SSL**<br>Allows Azure Stack Hub to communicate encrypted with Microsoft Active Directory Global Catalog Servers.|Active Directory Forest provided for Graph integration|TCP 3269|Public VIP - /27|Required when Azure Stack Hub is deployed using AD FS.|
-|**AD FS**<br>Allows Azure Stack Hub to communicate with on-premise AD FS.|AD FS metadata endpoint provided for AD FS integration|TCP 443|Public VIP - /27|Optional. The AD FS claims provider trust can be created using a [metadata file](../../operator/azure-stack-integrate-identity.md#setting-up-ad-fs-integration-by-providing-federation-metadata-file).|
+|**AD FS**<br>Allows Azure Stack Hub to communicate with on-premise AD FS.|AD FS metadata endpoint provided for AD FS integration|TCP 443|Public VIP - /27|Optional. The AD FS claims provider trust can be created using a [metadata file](../../operator/azure-stack-integrate-identity.md#set-up-ad-fs-integration-by-providing-federation-metadata-file).|
 |**Diagnostic log collection**<br>Allows Azure Stack Hub to send logs either proactively or manually by an operator to Microsoft support.|`https://*.blob.core.windows.net`<br>`https://azsdiagprdlocalwestus02.blob.core.windows.net`<br>`https://azsdiagprdwestusfrontend.westus.cloudapp.azure.com`<br>`https://azsdiagprdwestusfrontend.westus.cloudapp.azure.com` | HTTPS 443 | Public VIP - /27 |Not required. You can [save logs locally](../../operator/diagnostic-log-collection.md#save-logs-locally).|
 
 Outbound URLs are load balanced using Azure traffic manager to provide the best possible connectivity based on geographic location. With load balanced URLs, Microsoft can update and change backend endpoints without affecting customers. Microsoft doesn't share the list of IP addresses for the load balanced URLs. Use a device that supports filtering by URL rather than by IP.