Merge pull request MicrosoftDocs#419 from mspnp/locale-links

removing hard-coded locales from URLs

docs/antipatterns/chatty-io/index.md

@@ -212,7 +212,7 @@ await SaveCustomerListToFileAsync(customers);
 
 - When writing data, avoid locking resources for longer than necessary, to reduce the chances of contention during a lengthy operation. If a write operation spans multiple data stores, files, or services, then adopt an eventually consistent approach. See [Data Consistency guidance][data-consistency-guidance].
 
-- If you buffer data in memory before writing it, the data is vulnerable if the process crashes. If the data rate typically has bursts or is relatively sparse, it may be safer to buffer the data in an external durable queue such as [Event Hubs](http://azure.microsoft.com/en-us/services/event-hubs/).
+- If you buffer data in memory before writing it, the data is vulnerable if the process crashes. If the data rate typically has bursts or is relatively sparse, it may be safer to buffer the data in an external durable queue such as [Event Hubs](http://azure.microsoft.com/services/event-hubs/).
 
 - Consider caching data that you retrieve from a service or a database. This can help to reduce the volume of I/O by avoiding repeated requests for the same data. For more information, see [Caching best practices][caching-guidance].
 

docs/aws-professional/index.md

@@ -513,9 +513,9 @@ services that provide similar functionality:
     components within the Azure platform.
 
 -   [Service
-    Bus](https://azure.microsoft.com/en-us/services/service-bus/) - a more robust messaging system for connecting applications, services, and
+    Bus](https://azure.microsoft.com/services/service-bus/) - a more robust messaging system for connecting applications, services, and
     devices. Using the related [Service Bus
-    relay](https://docs.microsoft.com/en-us/azure/service-bus-relay/relay-what-is-it),
+    relay](https://docs.microsoft.com/azure/service-bus-relay/relay-what-is-it),
     Service Bus can also connect to remotely hosted applications and services.
 
 #### Device Farm

docs/best-practices/auto-scaling.md

@@ -75,7 +75,7 @@ Consider the following points when using Azure autoscale:
 * Configure the autoscaling rules, and then monitor the performance of your application over time. Use the results of this monitoring to adjust the way in which the system scales if necessary. However, keep in mind that autoscaling is not an instantaneous process. It takes time to react to a metric such as average CPU utilization exceeding (or falling below) a specified threshold.
 * Autoscaling rules that use a detection mechanism based on a measured trigger attribute (such as CPU usage or queue length) use an aggregated value over time, rather than instantaneous values, to trigger an autoscaling action. By default, the aggregate is an average of the values. This prevents the system from reacting too quickly, or causing rapid oscillation. It also allows time for new instances that are auto-started to settle into running mode, preventing additional autoscaling actions from occurring while the new instances are starting up. For Azure Cloud Services and Azure Virtual Machines, the default period for the aggregation is 45 minutes, so it can take up to this period of time for the metric to trigger autoscaling in response to spikes in demand. You can change the aggregation period by using the SDK, but be aware that periods of fewer than 25 minutes may cause unpredictable results (for more information, see [Auto Scaling Cloud Services on CPU Percentage with the Azure Monitoring Services Management Library](http://rickrainey.com/2013/12/15/auto-scaling-cloud-services-on-cpu-percentage-with-the-windows-azure-monitoring-services-management-library/)). For Web Apps, the averaging period is much shorter, allowing new instances to be available in about five minutes after a change to the average trigger measure.
 * If you configure autoscaling using the SDK rather than the portal, you can specify a more detailed schedule during which the rules are active. You can also create your own metrics and use them with or without any of the existing ones in your autoscaling rules. For example, you may wish to use alternative counters, such as the number of requests per second or the average memory availability, or use custom counters that measure specific business processes.
-* When autoscaling Service Fabric, the node types in your cluster are made of VM scale sets at the backend, so you need to set up auto-scale rules for each node type. Take into account the number of nodes that you must have before you set up auto-scaling. The minimum number of nodes that you must have for the primary node type is driven by the reliability level you have chosen. For more info, see [scale a Service Fabric cluster in or out using auto-scale rules](https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-cluster-scale-up-down).
+* When autoscaling Service Fabric, the node types in your cluster are made of VM scale sets at the backend, so you need to set up auto-scale rules for each node type. Take into account the number of nodes that you must have before you set up auto-scaling. The minimum number of nodes that you must have for the primary node type is driven by the reliability level you have chosen. For more info, see [scale a Service Fabric cluster in or out using auto-scale rules](https://docs.microsoft.com/azure/service-fabric/service-fabric-cluster-scale-up-down).
 * You can use the portal to link resources such as SQL Database instances and queues to a Cloud Service instance. This allows you to more easily access the separate manual and automatic scaling configuration options for each of the linked resources. For more information, see [How to: Link a resource to a cloud service](/azure/cloud-services/cloud-services-how-to-manage).
 * When you configure multiple policies and rules, they could conflict with each other. Autoscale uses the following conflict resolution rules to ensure that there is always a sufficient number of instances running:
   * Scale out operations always take precedence over scale in operations.

docs/best-practices/retry-service-specific.md

@@ -412,7 +412,7 @@ using (var db = new BloggingContext())
 
 ### More information
 * [Connection Resiliency](/ef/core/miscellaneous/connection-resiliency)
-* [Data Points - EF Core 1.1](https://msdn.microsoft.com/en-us/magazine/mt745093.aspx)
+* [Data Points - EF Core 1.1](https://msdn.microsoft.com/magazine/mt745093.aspx)
 
 ## SQL Database using ADO.NET retry guidelines
 SQL Database is a hosted SQL database available in a range of sizes and as both a standard (shared) and premium (non-shared) service.

docs/checklist/dev-ops.md

@@ -122,7 +122,7 @@ Shared documentation is critical. Encourage team members to contribute and share
 
 **Use configuration management.** Configuration changes should be planned, visible to operations, and recorded. This could take the form of a configuration management database, or a configuration-as-code approach. Configuration should be audited regularly to ensure that what's expected is actually in place.
 
-**Get an Azure support plan and understand the process.** Azure offers a number of [support plans][azure-support-plans]. Determine the right plan for your needs, and make sure the entire team knows how to use it. Team members should understand the details of the plan, how the support process works, and how to open a support ticket with Azure. If you are anticipating a high-scale event, Azure support can assist you with increasing your service limits. For more information, see the [Azure Support FAQs](https://azure.microsoft.com/en-us/support/faq/).
+**Get an Azure support plan and understand the process.** Azure offers a number of [support plans][azure-support-plans]. Determine the right plan for your needs, and make sure the entire team knows how to use it. Team members should understand the details of the plan, how the support process works, and how to open a support ticket with Azure. If you are anticipating a high-scale event, Azure support can assist you with increasing your service limits. For more information, see the [Azure Support FAQs](https://azure.microsoft.com/support/faq/).
 
 **Follow least-privilege principles when granting access to resources.** Carefully manage access to resources. Access should be denied by default, unless a user is explicitly given access to a resource. Only grant a user access to what they need to complete their tasks. Track user permissions and perform regular security audits.
 

docs/cloud-adoption-guide/adoption-intro/subscription-explainer.md

@@ -19,10 +19,10 @@ Organizations can use subscriptions to manage costs and creation of resource by
 * Now that you have learned about Azure subscriptions, learn more about [creating a subscription](subscription.md) before you create your first Azure resources..
 
 <!-- Links -->
-[azure-get-started]: https://azure.microsoft.com/en-us/get-started/
-[azure-offers]: https://azure.microsoft.com/en-us/support/legal/offer-details/
-[azure-free-trial]: https://azure.microsoft.com/en-us/offers/ms-azr-0044p/
+[azure-get-started]: https://azure.microsoft.com/get-started/
+[azure-offers]: https://azure.microsoft.com/support/legal/offer-details/
+[azure-free-trial]: https://azure.microsoft.com/offers/ms-azr-0044p/
 [azure-change-subscription-offer]: /azure/billing/billing-how-to-switch-azure-offer
 [microsoft-account]: https://account.microsoft.com/account
 [subscription-service-limits]: /azure/azure-subscription-service-limits
-[docs-organizational-account]: https://docs.microsoft.com/en-us/azure/active-directory/sign-up-organization
+[docs-organizational-account]: https://docs.microsoft.com/azure/active-directory/sign-up-organization

docs/guide/architecture-styles/event-driven.md

@@ -85,7 +85,7 @@ The boxes that are shaded gray show components of an IoT system that are not dir
  <!-- links -->
 
 [competing-consumers]: ../../patterns/competing-consumers.md
-[iot-ref-arch]: https://azure.microsoft.com/en-us/updates/microsoft-azure-iot-reference-architecture-available/
+[iot-ref-arch]: https://azure.microsoft.com/updates/microsoft-azure-iot-reference-architecture-available/
 [minimize-coordination]: ../design-principles/minimize-coordination.md
 
 

docs/patterns/cache-aside.md

@@ -120,7 +120,7 @@ public async Task<MyEntity> GetMyEntityAsync(int id)
 }
 ```
 
->  The examples use the Azure Redis Cache API to access the store and retrieve information from the cache. For more information, see [Using Microsoft Azure Redis Cache](https://docs.microsoft.com/en-us/azure/redis-cache/cache-dotnet-how-to-use-azure-redis-cache) and [How to create a Web App with Redis Cache](https://docs.microsoft.com/en-us/azure/redis-cache/cache-web-app-howto)
+>  The examples use the Azure Redis Cache API to access the store and retrieve information from the cache. For more information, see [Using Microsoft Azure Redis Cache](https://docs.microsoft.com/azure/redis-cache/cache-dotnet-how-to-use-azure-redis-cache) and [How to create a Web App with Redis Cache](https://docs.microsoft.com/azure/redis-cache/cache-web-app-howto)
 
 The `UpdateEntityAsync` method shown below demonstrates how to invalidate an object in the cache when the value is changed by the application. The code updates the original data store and then removes the cached item from the cache.
 
@@ -146,6 +146,6 @@ public async Task UpdateEntityAsync(MyEntity entity)
 
 The following information may be relevant when implementing this pattern:
 
-- [Caching Guidance](https://docs.microsoft.com/en-us/azure/architecture/best-practices/caching). Provides additional information on how you can cache data in a cloud solution, and the issues that you should consider when you implement a cache.
+- [Caching Guidance](https://docs.microsoft.com/azure/architecture/best-practices/caching). Provides additional information on how you can cache data in a cloud solution, and the issues that you should consider when you implement a cache.
 
 - [Data Consistency Primer](https://msdn.microsoft.com/library/dn589800.aspx). Cloud applications typically use data that's spread across data stores. Managing and maintaining data consistency in this environment is a critical aspect of the system, particularly the concurrency and availability issues that can arise. This primer describes issues about consistency across distributed data, and summarizes how an application can implement eventual consistency to maintain the availability of data.

docs/patterns/retry.md

@@ -45,7 +45,7 @@ The application should wrap all attempts to access a remote service in code that
 
 An application should log the details of faults and failing operations. This information is useful to operators. If a service is frequently unavailable or busy, it's often because the service has exhausted its resources. You can reduce the frequency of these faults by scaling out the service. For example, if a database service is continually overloaded, it might be beneficial to partition the database and spread the load across multiple servers.
 
-> [Microsoft Entity Framework](https://docs.microsoft.com/ef/) provides facilities for retrying database operations. Also, most Azure services and client SDKs include a retry mechanism. For more information, see [Retry guidance for specific services](https://docs.microsoft.com/en-us/azure/architecture/best-practices/retry-service-specific).
+> [Microsoft Entity Framework](https://docs.microsoft.com/ef/) provides facilities for retrying database operations. Also, most Azure services and client SDKs include a retry mechanism. For more information, see [Retry guidance for specific services](https://docs.microsoft.com/azure/architecture/best-practices/retry-service-specific).
 
 ## Issues and considerations
 
@@ -169,5 +169,5 @@ private bool IsTransient(Exception ex)
 ## Related patterns and guidance
 
 - [Circuit Breaker pattern](circuit-breaker.md). The Retry pattern is useful for handling transient faults. If a failure is expected to be more long lasting, it might be more appropriate to implement the Circuit Breaker pattern. The Retry pattern can also be used in conjunction with a circuit breaker to provide a comprehensive approach to handling faults.
-- [Retry guidance for specific services](https://docs.microsoft.com/en-us/azure/architecture/best-practices/retry-service-specific)
-- [Connection Resiliency](https://docs.microsoft.com/en-us/ef/core/miscellaneous/connection-resiliency)
+- [Retry guidance for specific services](https://docs.microsoft.com/azure/architecture/best-practices/retry-service-specific)
+- [Connection Resiliency](https://docs.microsoft.com/ef/core/miscellaneous/connection-resiliency)

docs/reference-architectures/sharepoint/index.md

@@ -285,7 +285,7 @@ The following table shows the VMs that are deployed.
 [availability-set]: /azure/virtual-machines/windows/manage-availability
 [azure-portal]: https://portal.azure.com
 [azure-ps]: /powershell/azure/overview
-[azure-pricing]: https://azure.microsoft.com/en-us/pricing/calculator/
+[azure-pricing]: https://azure.microsoft.com/pricing/calculator/
 [bastion-host]: https://en.wikipedia.org/wiki/Bastion_host
 [create-availability-group]: https://technet.microsoft.com/library/mt793548(v=office.16).aspx
 [connect-to-vm]: /azure/virtual-machines/windows/quick-create-portal#connect-to-virtual-machine

docs/reference-architectures/virtual-machines-windows/single-vm.md

@@ -194,7 +194,7 @@ For more information on deploying this sample reference architecture, visit our
 [fqdn]: /azure/virtual-machines/virtual-machines-windows-portal-create-fqdn
 [git]: https://github.com/mspnp/reference-architectures/tree/master/virtual-machines/single-vm
 [github-folder]: https://github.com/mspnp/reference-architectures/tree/master/virtual-machines/single-vm
-[group-policy]: https://technet.microsoft.com/en-us/library/dn595129.aspx
+[group-policy]: https://docs.microsoft.com/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn595129(v=ws.11)
 [log-collector]: https://azure.microsoft.com/blog/simplifying-virtual-machine-troubleshooting-using-azure-log-collector/
 [manage-vm-availability]: /azure/virtual-machines/virtual-machines-windows-manage-availability
 [multi-vm]: multi-vm.md