updating links from fwlink to real link if exists (#16673)

* updating links from fwlink to real link if exists - contributes to #3391

* Apply suggestions from code review

Co-Authored-By: Maira Wenzel <[email protected]>

Co-authored-by: Maira Wenzel <[email protected]>

Author: eddynaka

docs/framework/wcf/feature-details/deploying-an-internet-information-services-hosted-wcf-service.md

@@ -31,13 +31,13 @@ The installation process for .NET Framework automatically registers WCF with IIS
 
 - Windows 7 and Windows Server 2003: Use the [ServiceModel Registration Tool (ServiceModelReg.exe)](../../../../docs/framework/wcf/servicemodelreg-exe.md) tool to register WCF with IIS. To use this tool, type **ServiceModelReg.exe /i /x** in the [Developer Command Prompt for Visual Studio](../../tools/developer-command-prompt-for-vs.md).
 
-- Windows 7: Finally, you must verify that ASP.NET is configured to use the .NET Framework version 4 or later. You do this by running the ASPNET_Regiis tool with the `–i` option. For more information, see [ASP.NET IIS Registration Tool](https://go.microsoft.com/fwlink/?LinkId=201186).
+- Windows 7: Finally, you must verify that ASP.NET is configured to use the .NET Framework version 4 or later. You do this by running the ASPNET_Regiis tool with the `–i` option. For more information, see [ASP.NET IIS Registration Tool](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/k6h9cz8h(v=vs.90)).
 
 ## Create a New IIS Application or Reuse an Existing ASP.NET Application
 
 IIS-hosted WCF services must reside inside of an IIS application. You can create a new IIS application to host WCF services exclusively. Alternatively, you can deploy an WCF service into an existing application that is already hosting ASP.NET 2.0 content (such as .aspx pages and ASP.NET Web services [ASMX]). For more information about these options, see the "Hosting WCF Side-by-Side with ASP.NET" and "Hosting WCF Services in ASP.NET Compatibility Mode" sections in [WCF Services and ASP.NET](wcf-services-and-aspnet.md).
 
-Note that IIS 6.0 and later versions periodically restart an isolated object-oriented programming application. The default value is 1740 minutes. The maximum value supported is 71,582 minutes. This restart can be disabled. For more information about this property, see the [PeriodicRestartTime](https://go.microsoft.com/fwlink/?LinkId=109968).
+Note that IIS 6.0 and later versions periodically restart an isolated object-oriented programming application. The default value is 1740 minutes. The maximum value supported is 71,582 minutes. This restart can be disabled. For more information about this property, see the [PeriodicRestartTime](https://docs.microsoft.com/previous-versions/iis/6.0-sdk/ms525914(v=vs.90)).
 
 ## Create an .svc File for the WCF Service
 
@@ -65,7 +65,7 @@ WCF services hosted in IIS use the same dynamic compilation model as ASP.NET 2.0
 
 - As uncompiled code placed directly in the .svc file. Implementation code can also be located inline in the service’s .svc file, after the \@ServiceHost directive. Any changes to inline code cause the application to be recycled and recompiled when the next request is received.
 
-For more information about the ASP.NET 2.0 compilation model, see [ASP.NET Compilation Overview](https://go.microsoft.com/fwlink/?LinkId=94773).
+For more information about the ASP.NET 2.0 compilation model, see [ASP.NET Compilation Overview](https://docs.microsoft.com/previous-versions/aspnet/ms178466(v=vs.100)).
 
 ## Configure the WCF Service
 
@@ -107,4 +107,4 @@ For example, a WCF endpoint configured to use HTTP digest authentication must re
 
 - [Hosting in Internet Information Services](hosting-in-internet-information-services.md)
 - [Internet Information Services Hosting Best Practices](internet-information-services-hosting-best-practices.md)
-- [Windows Server App Fabric Hosting Features](https://go.microsoft.com/fwlink/?LinkId=201276)
+- [Windows Server App Fabric Hosting Features](https://docs.microsoft.com/previous-versions/appfabric/ee677189(v=azure.10))

docs/framework/wcf/feature-details/discovery-find-and-findcriteria.md

@@ -5,7 +5,7 @@ ms.assetid: 99016fa4-1778-495b-b4cc-0e22fbec42c6
 ---
 # Discovery Find and FindCriteria
 
-A discovery find operation is initiated by a client to discover one or more services and is one of the main actions in discovery. Performing a find sends a WS-Discovery Probe message over the network. Services that match the criteria specified reply with WS-Discovery ProbeMatch messages. For more information about discovery messages, see the [WS-Discovery specification](https://go.microsoft.com/fwlink/?LinkID=122347).
+A discovery find operation is initiated by a client to discover one or more services and is one of the main actions in discovery. Performing a find sends a WS-Discovery Probe message over the network. Services that match the criteria specified reply with WS-Discovery ProbeMatch messages. For more information about discovery messages, see the [WS-Discovery specification](http://schemas.xmlsoap.org/ws/2004/10/discovery/ws-discovery.pdf).
 
 ## DiscoveryClient
 

docs/framework/wcf/feature-details/distributed-application-security.md

@@ -59,8 +59,8 @@ Windows Communication Foundation (WCF) security is broken into three major funct
 |Setting|Description|  
 |-------------|-----------------|  
 |None|Specifies that the client does not need to present any credential. This translates to an anonymous client.|  
-|Basic|Specifies basic authentication.  For additional information, see RFC2617, "[HTTP Authentication: Basic and Digest Authentication](https://go.microsoft.com/fwlink/?LinkId=88313)."|  
-|Digest|Specifies digest authentication.  For additional information, see RFC2617, "[HTTP Authentication: Basic and Digest Authentication](https://go.microsoft.com/fwlink/?LinkId=88313)."|  
+|Basic|Specifies basic authentication. For more information, see RFC2617, "[HTTP Authentication: Basic and Digest Authentication](http://schemas.xmlsoap.org/ws/2004/10/discovery/ws-discovery.pdf)."|  
+|Digest|Specifies digest authentication. For more information, see RFC2617, "[HTTP Authentication: Basic and Digest Authentication](http://schemas.xmlsoap.org/ws/2004/10/discovery/ws-discovery.pdf)."|  
 |Ntlm|Specifies Windows authentication using SSPI negotiation on a Windows domain.<br /><br /> SSPI negotiation results in using either the Kerberos protocol or NT LanMan (NTLM).|  
 |Windows|Specifies Windows authentication using SSPI on a Windows domain. SSPI picks from either the Kerberos protocol or NTLM as authentication service.<br /><br /> SSPI tries Kerberos protocol first; if that fails, it then uses NTLM.|  
 |Certificate|Performs client authentication using a certificate, typically X.509.|  
@@ -93,4 +93,4 @@ Windows Communication Foundation (WCF) security is broken into three major funct
 - [Endpoint Creation Overview](../../../../docs/framework/wcf/endpoint-creation-overview.md)
 - [System-Provided Bindings](../../../../docs/framework/wcf/system-provided-bindings.md)
 - [Security Overview](../../../../docs/framework/wcf/feature-details/security-overview.md)
-- [Security Model for Windows Server App Fabric](https://go.microsoft.com/fwlink/?LinkID=201279&clcid=0x409)
+- [Security Model for Windows Server App Fabric](https://docs.microsoft.com/previous-versions/appfabric/ee677202(v=azure.10))

docs/framework/wcf/feature-details/extended-protection-for-authentication-overview.md

@@ -28,4 +28,4 @@ Extended Protection for Authentication helps protect against man-in-the-middle (
 
 ## See also
 
-- [Security Model for Windows Server App Fabric](https://go.microsoft.com/fwlink/?LinkID=201279&clcid=0x409)
+- [Security Model for Windows Server App Fabric](https://docs.microsoft.com/previous-versions/appfabric/ee677202(v=azure.10))

docs/framework/wcf/feature-details/federation-and-issued-tokens.md

@@ -59,4 +59,4 @@ With Windows Communication Foundation (WCF), you can create clients that communi
 
 - [Authorization](../../../../docs/framework/wcf/feature-details/authorization-in-wcf.md)
 - [Custom Tokens](../../../../docs/framework/wcf/extending/custom-tokens.md)
-- [Security Model for Windows Server App Fabric](https://go.microsoft.com/fwlink/?LinkID=201279&clcid=0x409)
+- [Security Model for Windows Server App Fabric](https://docs.microsoft.com/previous-versions/appfabric/ee677202(v=azure.10))

docs/framework/wcf/feature-details/filtering.md

@@ -39,7 +39,7 @@ The Windows Communication Foundation (WCF) filtering system can use declarative
 1. The <xref:System.ServiceModel.Dispatcher.PrefixEndpointAddressMessageFilter> functions just like the <xref:System.ServiceModel.Dispatcher.EndpointAddressMessageFilter> filter, except that the match can be on a prefix of the message URI. For example, a filter specifying the address `http://www.adatum.com` matches messages addressed to `http://www.adatum.com/userA`.  
 
 ### XPath Message Filters  
- An <xref:System.ServiceModel.Dispatcher.XPathMessageFilter> uses an XPath expression to determine whether an XML document contains specific elements, attributes, text, or other XML syntactic constructs. The filter is optimized to be extremely efficient for a strict subset of XPath. The XML Path Language is described in the [W3C XML Path Language 1.0 specification](https://go.microsoft.com/fwlink/?LinkId=94779).  
+ An <xref:System.ServiceModel.Dispatcher.XPathMessageFilter> uses an XPath expression to determine whether an XML document contains specific elements, attributes, text, or other XML syntactic constructs. The filter is optimized to be extremely efficient for a strict subset of XPath. The XML Path Language is described in the [W3C XML Path Language 1.0 specification](https://www.w3.org/TR/xpath/all/).  
 
  Typically, an application uses an <xref:System.ServiceModel.Dispatcher.XPathMessageFilter> at an endpoint to query the contents of a SOAP message and then takes the appropriate action based on the results of that query. A queuing process, for example, may use an XPath query to inspect the priority element of a known header to decide whether to move a message to the front of the queue.  
 

docs/framework/wcf/feature-details/generating-a-wcf-client-from-service-metadata.md

@@ -12,7 +12,7 @@ This topic describes how to use the various switches in Svcutil.exe to generate
 
 - MEX request to the supplied address with `/mex` appended.  
 
-- DISCO request (using the [DiscoveryClientProtocol](https://go.microsoft.com/fwlink/?LinkId=94777) from ASP.NET Web services) to the supplied address.  
+- DISCO request (using the <xref:System.Web.Services.Discovery.DiscoveryClientProtocol> from ASP.NET Web services) to the supplied address.  
 
  Svcutil.exe generates the client based on the Web Services Description Language (WSDL) or policy file received from the service. The user principal name (UPN) is generated by concatenating the user name with "\@" and then adding a fully-qualified domain name (FQDN). However, for users who registered on Active Directory, this format is not valid and the UPN that the tool generates causes a failure in the Kerberos authentication with the following error message: **The logon attempt failed.** To resolve this problem, manually fix the client file that the tool generated.  
 
@@ -41,7 +41,7 @@ svcutil.exe [/t:code]  <metadataDocumentPath>* | <url>* | <epr>
 
 |Option|Description|  
 |------------|-----------------|  
-|**/language:\<language>**|Specifies the programming language to use for code generation. Provide either a language name registered in the Machine.config file or the fully-qualified name of a class that inherits from <xref:System.CodeDom.Compiler.CodeDomProvider>.<br /><br /> Values: c#, cs, csharp, vb, vbs, visualbasic, vbscript, javascript, c++, mc, cpp<br /><br /> Default: csharp<br /><br /> Short form: `/l`<br /><br /> For more information, see [CodeDomProvider Class](https://go.microsoft.com/fwlink/?LinkId=94778).|  
+|**/language:\<language>**|Specifies the programming language to use for code generation. Provide either a language name registered in the Machine.config file or the fully-qualified name of a class that inherits from <xref:System.CodeDom.Compiler.CodeDomProvider>.<br /><br /> Values: c#, cs, csharp, vb, vbs, visualbasic, vbscript, javascript, c++, mc, cpp<br /><br /> Default: csharp<br /><br /> Short form: `/l`<br /><br /> For more information, see <xref:System.CodeDom.Compiler.CodeDomProvider> class.|  
 
 ## Choosing a Namespace for the Client  
 

docs/framework/wcf/feature-details/hosting-in-a-windows-service-application.md

@@ -37,4 +37,4 @@ Windows services (formerly known as Windows NT services) provide a process model
 - [How to: Host a WCF Service in a Managed Windows Service](../../../../docs/framework/wcf/feature-details/how-to-host-a-wcf-service-in-a-managed-windows-service.md)
 - [Windows Service Host](../../../../docs/framework/wcf/samples/windows-service-host.md)
 - [Service Application Programming Architecture](https://go.microsoft.com/fwlink/?LinkId=94876)
-- [Windows Server App Fabric Hosting Features](https://go.microsoft.com/fwlink/?LinkId=201276)
+- [Windows Server App Fabric Hosting Features](https://docs.microsoft.com/previous-versions/appfabric/ee677189(v=azure.10))

docs/framework/wcf/feature-details/hosting-in-internet-information-services.md

@@ -19,7 +19,7 @@ WCF can be hosted on the following versions of IIS on the following operating sy
 
 - IIS 7.0 on Windows Vista and Windows Server 2008. IIS 7.0 provides the same advanced process model as IIS 6.0, but uses the Windows Process Activation Service (WAS) to allow activation and network communication over protocols other than HTTP. This environment is suitable for the development of WCF services that communicate over any network protocol supported by WCF (including HTTP, net.tcp, net.pipe, and net.msmq). For more information about WAS, see [Hosting in Windows Process Activation Service](../../../../docs/framework/wcf/feature-details/hosting-in-windows-process-activation-service.md).
 
-- [Windows Server AppFabric](https://go.microsoft.com/fwlink/?LinkId=196496) works with IIS 7.0 and Windows Process Activation Service (WAS) to provide a rich application hosting environment for NET4 WCF and WF services. These benefits include process life-cycle management, process recycling, shared hosting, rapid failure protection, process orphaning, on-demand activation, and health monitoring. For detailed information, see [AppFabric Hosting Features](https://go.microsoft.com/fwlink/?LinkId=196494) and [AppFabric Hosting Concepts](https://go.microsoft.com/fwlink/?LinkId=196495).
+- [Windows Server AppFabric](https://docs.microsoft.com/previous-versions/appfabric/ff384253(v=azure.10)) works with IIS 7.0 and Windows Process Activation Service (WAS) to provide a rich application hosting environment for NET4 WCF and WF services. These benefits include process life-cycle management, process recycling, shared hosting, rapid failure protection, process orphaning, on-demand activation, and health monitoring. For detailed information, see [AppFabric Hosting Features](https://docs.microsoft.com/previous-versions/appfabric/ee677189(v=azure.10)) and [AppFabric Hosting Concepts](https://docs.microsoft.com/previous-versions/appfabric/ee677371(v=azure.10)).
 
 ## Benefits of IIS hosting
 
@@ -62,4 +62,4 @@ WCF services can be hosted either side-by-side with ASP.NET or in ASP.NET Compat
 - [WCF Services and ASP.NET](../../../../docs/framework/wcf/feature-details/wcf-services-and-aspnet.md)
 - [Internet Information Services Hosting Best Practices](../../../../docs/framework/wcf/feature-details/internet-information-services-hosting-best-practices.md)
 - [Configuring Internet Information Services 7.0 for Windows Communication Foundation](../../../../docs/framework/wcf/feature-details/configuring-iis-for-wcf.md)
-- [Windows Server App Fabric Hosting Features](https://go.microsoft.com/fwlink/?LinkId=201276)
+- [Windows Server App Fabric Hosting Features](https://docs.microsoft.com/previous-versions/appfabric/ee677189(v=azure.10))

docs/framework/wcf/feature-details/hosting-in-windows-process-activation-service.md

@@ -19,7 +19,7 @@ The Windows Process Activation Service (WAS) manages the activation and lifetime
 - Centralized application configuration and management.  
 
 - Allows applications to take advantage of the IIS process model without requiring the deployment footprint of a full IIS installation.  
-[Windows Server AppFabric](https://go.microsoft.com/fwlink/?LinkId=196496) works with IIS 7.0 and Windows Process Activation Service (WAS) to provide a rich application hosting environment for NET4 WCF and WF services. These benefits include process life-cycle management, process recycling, shared hosting, rapid failure protection, process orphaning, on-demand activation, and health monitoring. For detailed information, see [AppFabric Hosting Features](https://go.microsoft.com/fwlink/?LinkId=196494) and [AppFabric Hosting Concepts](https://go.microsoft.com/fwlink/?LinkId=196495).  
+[Windows Server AppFabric](https://docs.microsoft.com/previous-versions/appfabric/ff384253(v=azure.10)) works with IIS 7.0 and Windows Process Activation Service (WAS) to provide a rich application hosting environment for NET4 WCF and WF services. These benefits include process life-cycle management, process recycling, shared hosting, rapid failure protection, process orphaning, on-demand activation, and health monitoring. For detailed information, see [AppFabric Hosting Features](https://docs.microsoft.com/previous-versions/appfabric/ee677189(v=azure.10)) and [AppFabric Hosting Concepts](https://docs.microsoft.com/previous-versions/appfabric/ee677371(v=azure.10)).  
 
 ## Elements of the WAS Addressing Model  
  Applications have Uniform Resource Identifier (URI) addresses, which are the code units whose lifetime and execution environment are managed by the server. A single WAS server instance can be home to many different applications. Servers organize applications into groups called *sites*. Within a site, applications are arranged in a hierarchical manner that reflects the structure of the URIs that serve as their external addresses.  
@@ -48,4 +48,4 @@ The Windows Process Activation Service (WAS) manages the activation and lifetime
 - [Configuring WAS for Use with WCF](../../../../docs/framework/wcf/feature-details/configuring-the-wpa--service-for-use-with-wcf.md)
 - [How to: Install and Configure WCF Activation Components](../../../../docs/framework/wcf/feature-details/how-to-install-and-configure-wcf-activation-components.md)
 - [How to: Host a WCF Service in WAS](../../../../docs/framework/wcf/feature-details/how-to-host-a-wcf-service-in-was.md)
-- [Windows Server App Fabric Hosting Features](https://go.microsoft.com/fwlink/?LinkId=201276)
+- [Windows Server App Fabric Hosting Features](https://docs.microsoft.com/previous-versions/appfabric/ee677189(v=azure.10))