From 491d02a0afdbb2c60d6dba5a69003846e89b59bd Mon Sep 17 00:00:00 2001 From: Christopher Bennage Date: Tue, 20 Feb 2018 14:36:54 -0800 Subject: [PATCH] removing hard-coded locales from URLs --- docs/antipatterns/chatty-io/index.md | 2 +- docs/aws-professional/index.md | 4 ++-- docs/aws-professional/services.md | 18 +++++++++--------- docs/best-practices/auto-scaling.md | 2 +- docs/best-practices/retry-service-specific.md | 2 +- docs/checklist/dev-ops.md | 2 +- .../adoption-intro/subscription-explainer.md | 8 ++++---- docs/guide/architecture-styles/event-driven.md | 2 +- docs/patterns/cache-aside.md | 4 ++-- docs/patterns/retry.md | 6 +++--- .../sharepoint/index.md | 2 +- .../virtual-machines-windows/single-vm.md | 2 +- .../disaster-recovery-azure-applications.md | 4 ++-- docs/resources/diagrams.md | 2 +- .../migrate-from-cloud-services.md | 8 ++++---- docs/service-fabric/refactor-migrated-app.md | 2 +- 16 files changed, 35 insertions(+), 35 deletions(-) diff --git a/docs/antipatterns/chatty-io/index.md b/docs/antipatterns/chatty-io/index.md index b2660bf7108..f5dbfe30634 100644 --- a/docs/antipatterns/chatty-io/index.md +++ b/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]. diff --git a/docs/aws-professional/index.md b/docs/aws-professional/index.md index 59b52a5d05a..52b1ab6ca26 100644 --- a/docs/aws-professional/index.md +++ b/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 diff --git a/docs/aws-professional/services.md b/docs/aws-professional/services.md index 49c19b21873..348b4e73327 100644 --- a/docs/aws-professional/services.md +++ b/docs/aws-professional/services.md @@ -37,10 +37,10 @@ For an overview of Azure for AWS users, see [Introduction to Azure for AWS profe | ** ** | Amazon Lightsail | [Azure Virtual Machines & Images](https://azure.microsoft.com/services/virtual-machines/) | Collection of virtual machine templates to select from when building out your virtual machine. | | Container instances | EC2 Container Service (ECS) | [Azure Container Service](https://azure.microsoft.com/services/container-service/) | Azure Container Instances is the fastest and simplest way to run a container in Azure, without having to provision any virtual machines or adopt a higher-level orchestration service. | | ** ** | EC2 Container Registry | [Azure Container Registry](https://azure.microsoft.com/services/container-registry/) | Allows customers to store Docker formatted images. Used to create all types of container deployments on Azure. -| Microservices / container orchestrators | Elastic Container Service for Kubernetes (EKS) | [Azure Container Service (AKS)](https://azure.microsoft.com/en-us/services/container-service/) | Deploy orchestrated containerized applications with Kubernetes. Simplify monitoring and cluster management through auto upgrades and a built-in operations console. | +| Microservices / container orchestrators | Elastic Container Service for Kubernetes (EKS) | [Azure Container Service (AKS)](https://azure.microsoft.com/services/container-service/) | Deploy orchestrated containerized applications with Kubernetes. Simplify monitoring and cluster management through auto upgrades and a built-in operations console. | |   | | [Service Fabric](https://azure.microsoft.com/services/service-fabric/) | A compute service that orchestrates and manages the execution, lifetime, and resilience of complex, inter-related code components that can be either stateless or stateful. | |   | | [Azure Container Service (ACS)](/azure/container-service/) | Quickly deploy a production ready Kubernetes, DC/OS, or Docker Swarm cluster | -| Serverless | Lambda | [Azure Functions](https://azure.microsoft.com/services/functions/)

[Azure Event Grid](https://azure.microsoft.com/en-us/services/event-grid/) | Integrate systems and run backend processes in response to events or schedules without provisioning or managing servers. | +| Serverless | Lambda | [Azure Functions](https://azure.microsoft.com/services/functions/)

[Azure Event Grid](https://azure.microsoft.com/services/event-grid/) | Integrate systems and run backend processes in response to events or schedules without provisioning or managing servers. | | ** ** | Lambda @ Edge | [Functions on Azure IoT Edge](/azure/iot-edge/tutorial-deploy-function) | Runs functions at the edge (directly on IoT devices) even with intermittent cloud connectivity. | | Backend process logic |   | [Web Jobs](/azure/app-service-web/websites-webjobs-resources) | Provides an easy way to run background processes in an application context. | | Batch computing | AWS Batch | [Azure Batch](https://azure.microsoft.com/services/batch/) | Run large-scale parallel and high-performance computing applications efficiently in the cloud. | @@ -59,7 +59,7 @@ For an overview of Azure for AWS users, see [Introduction to Azure for AWS profe | Backup | None | [Azure Backup](https://azure.microsoft.com/services/backup/) | Backup and archival solutions allow files and folders to be backed up and recovered from the cloud, and provide off-site protection against data loss. There are two components of backup—the software service that orchestrates backup/retrieval and the underlying backup storage infrastructure. | | Hybrid storage | Storage Gateway | [StorSimple](https://azure.microsoft.com/services/storsimple/) | Integrates on-premises IT environments with cloud storage. Automates data management and storage, plus supports disaster recovery. | | Bulk data transfer | AWS Import/Export Disk | [Import/Export](https://azure.microsoft.com/documentation/articles/storage-import-export-service/) | A data transport solution that uses secure disks and appliances to transfer large amounts of data. Also offers data protection during transit. | -| ** ** | AWS Import/Export Snowball

AWS Snowball Edge

AWS Snowmobile | [Azure Data Box](https://azure.microsoft.com/en-us/services/storage/databox/) | Petabyte- to Exabyte-scale data transport solution that uses secure data storage devices to transfer large amounts of data into and out of the AWS cloud, at lower cost than Internet-based transfers. | +| ** ** | AWS Import/Export Snowball

AWS Snowball Edge

AWS Snowmobile | [Azure Data Box](https://azure.microsoft.com/services/storage/databox/) | Petabyte- to Exabyte-scale data transport solution that uses secure data storage devices to transfer large amounts of data into and out of the AWS cloud, at lower cost than Internet-based transfers. | | Disaster recovery | None | [Site Recovery](https://azure.microsoft.com/services/site-recovery/) | Automates protection and replication of virtual machines. Offers health monitoring, recovery plans, and recovery plan testing. | @@ -80,11 +80,11 @@ For an overview of Azure for AWS users, see [Introduction to Azure for AWS profe | Area | AWS Service | Azure Service | Description | |-------------------------|--------------------------------------|-----------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------| -| Relational database | RDS | [SQL Database](https://azure.microsoft.com/services/sql-database/)

[Azure Database for MySQL](https://azure.microsoft.com/en-us/services/mysql/)

[Azure Database for PostgreSQL](https://azure.microsoft.com/en-us/services/postgresql/) | Relational database-as-a-service (DBaaS) where the database resilience, scale, and maintenance are primarily handled by the platform. | +| Relational database | RDS | [SQL Database](https://azure.microsoft.com/services/sql-database/)

[Azure Database for MySQL](https://azure.microsoft.com/services/mysql/)

[Azure Database for PostgreSQL](https://azure.microsoft.com/services/postgresql/) | Relational database-as-a-service (DBaaS) where the database resilience, scale, and maintenance are primarily handled by the platform. | | NoSQL—document storage | DynamoDB | [Azure Cosmos DB](https://azure.microsoft.com/services/cosmos-db/) | A globally distributed, multi-model database that natively supports multiple data models: key-value, documents, graphs, and columnar. | | NoSQL—key/value storage | DynamoDB and SimpleDB | [Table Storage](https://azure.microsoft.com/services/storage/tables/) | A nonrelational data store for semi-structured data. Developers store and query data items via web services requests. | | Caching | ElastiCache | [Azure Redis Cache](https://azure.microsoft.com/services/cache/) | An in-memory–based, distributed caching service that provides a high-performance store typically used to offload nontransactional work from a database. | -| Database migration | Database Migration Service (Preview) | [Azure Database Migration Service](https://azure.microsoft.com/en-us/campaigns/database-migration/) | Typically is focused on the migration of database schema and data from one database format to a specific database technology in the cloud. | +| Database migration | Database Migration Service (Preview) | [Azure Database Migration Service](https://azure.microsoft.com/campaigns/database-migration/) | Typically is focused on the migration of database schema and data from one database format to a specific database technology in the cloud. | ## Analytics and big data @@ -94,15 +94,15 @@ For an overview of Azure for AWS users, see [Introduction to Azure for AWS profe | Elastic data warehouse | Redshift | [SQL Data Warehouse](https://azure.microsoft.com/services/sql-data-warehouse/) | A fully managed data warehouse that analyzes data using business intelligence tools. It can transact SQL queries across relational and nonrelational data. | | Big data processing | Elastic MapReduce (EMR) | [HDInsight](https://azure.microsoft.com/services/hdinsight/) | Supports technologies that break up large data processing tasks into multiple jobs, and then combine the results to enable massive parallelism. | | Data orchestration | Data Pipeline | [Data Factory](https://azure.microsoft.com/services/data-factory/) | Processes and moves data between different compute and storage services, as well as on-premises data sources at specified intervals. Users can create, schedule, orchestrate, and manage data pipelines. | -| ** ** | AWS Glue | [Data Factory](https://azure.microsoft.com/services/data-factory/)

[Data Catalog](https://azure.microsoft.com/en-us/services/data-catalog/) | Cloud-based ETL/data integration service that orchestrates and automates the movement and transformation of data from various sources. | +| ** ** | AWS Glue | [Data Factory](https://azure.microsoft.com/services/data-factory/)

[Data Catalog](https://azure.microsoft.com/services/data-catalog/) | Cloud-based ETL/data integration service that orchestrates and automates the movement and transformation of data from various sources. | | Analytics | Kinesis Analytics | [Stream Analytics](https://azure.microsoft.com/services/stream-analytics/)

[Data Lake Analytics](https://azure.microsoft.com/services/data-lake-analytics/)

[Data Lake Store](https://azure.microsoft.com/services/data-lake-store/) | Storage and analysis platforms that create insights from large quantities of data, or data that originates from many sources. | | Visualization | QuickSight (Preview) | [PowerBI](https://powerbi.microsoft.com/) | Business intelligence tools that build visualizations, perform ad hoc analysis, and develop business insights from data. | | ** ** | None | [Power BI Embedded](https://azure.microsoft.com/services/power-bi-embedded/) | Allows visualization and data analysis tools to be embedded in applications. | | Search | Elasticsearch Service | [Marketplace—Elasticsearch](https://azuremarketplace.microsoft.com/marketplace/apps?page=1&search=Elasticsearch) | A scalable search server based on Apache Lucene. | | ** ** | CloudSearch | [Azure Search](https://azure.microsoft.com/services/search/) | Delivers full-text search and related search analytics and capabilities. | -| Machine learning | Machine Learning | [Azure Machine Learning Studio](https://azure.microsoft.com/services/machine-learning/)

[Azure Machine Learning Workbench](https://azure.microsoft.com/en-us/services/machine-learning-services/) | Produces an end-to-end workflow to create, process, refine, and publish predictive models that can be used to understand what might happen from complex data sets. | +| Machine learning | Machine Learning | [Azure Machine Learning Studio](https://azure.microsoft.com/services/machine-learning/)

[Azure Machine Learning Workbench](https://azure.microsoft.com/services/machine-learning-services/) | Produces an end-to-end workflow to create, process, refine, and publish predictive models that can be used to understand what might happen from complex data sets. | | Data discovery | None | [Data Catalog](https://azure.microsoft.com/services/data-catalog/) | Provides the ability to better register, enrich, discover, understand, and consume data sources. | -| ** ** | Amazon Athena | [Azure Data Lake Analytics](https://azure.microsoft.com/en-us/services/data-lake-analytics/) | Provides a serverless interactive query service that uses standard SQL for analyzing databases. | +| ** ** | Amazon Athena | [Azure Data Lake Analytics](https://azure.microsoft.com/services/data-lake-analytics/) | Provides a serverless interactive query service that uses standard SQL for analyzing databases. | ## Intelligence @@ -179,7 +179,7 @@ For an overview of Azure for AWS users, see [Introduction to Azure for AWS profe | ** ** | Cognito | [Azure Active Directory B2C](https://azure.microsoft.com/services/active-directory-b2c/) | A highly available, global, identity management service for consumer-facing applications that scales to hundreds of millions of identities. | | ** ** | AWS Directory Service | [Windows Server Active Directory](https://azure.microsoft.com/services/active-directory-ds/) | Services for supporting Microsoft Active Directory in the cloud. | | Compliance | AWS Artifact | [Microsoft Service Trust Portal](https://www.microsoft.com/TrustCenter/STP/default.aspx) | Provides access to audit reports, compliance guides, and trust documents from across cloud services. | -| Security | AWS Shield | [Azure DDos Protection Service (Preview)](https://azure.microsoft.com/en-us/blog/azure-ddos-protection-service-preview/) | Provides cloud services with protection from distributed denial of services (DDoS) attacks. | +| Security | AWS Shield | [Azure DDos Protection Service (Preview)](https://azure.microsoft.com/blog/azure-ddos-protection-service-preview/) | Provides cloud services with protection from distributed denial of services (DDoS) attacks. | ## Developer tools diff --git a/docs/best-practices/auto-scaling.md b/docs/best-practices/auto-scaling.md index c1fe52e0dde..ce69f16573e 100644 --- a/docs/best-practices/auto-scaling.md +++ b/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. diff --git a/docs/best-practices/retry-service-specific.md b/docs/best-practices/retry-service-specific.md index c0f6122d41b..6ead3be831a 100644 --- a/docs/best-practices/retry-service-specific.md +++ b/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. diff --git a/docs/checklist/dev-ops.md b/docs/checklist/dev-ops.md index e12263d053b..0e6432c37cf 100644 --- a/docs/checklist/dev-ops.md +++ b/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. diff --git a/docs/cloud-adoption-guide/adoption-intro/subscription-explainer.md b/docs/cloud-adoption-guide/adoption-intro/subscription-explainer.md index 21d15ec4899..4aab2846fe4 100644 --- a/docs/cloud-adoption-guide/adoption-intro/subscription-explainer.md +++ b/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.. -[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 diff --git a/docs/guide/architecture-styles/event-driven.md b/docs/guide/architecture-styles/event-driven.md index d1b4580c5de..7b1e40c4566 100644 --- a/docs/guide/architecture-styles/event-driven.md +++ b/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 [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 diff --git a/docs/patterns/cache-aside.md b/docs/patterns/cache-aside.md index dd3664307cd..e5a432e8f60 100644 --- a/docs/patterns/cache-aside.md +++ b/docs/patterns/cache-aside.md @@ -120,7 +120,7 @@ public async Task 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. diff --git a/docs/patterns/retry.md b/docs/patterns/retry.md index fedb774f67f..56306ec27fd 100644 --- a/docs/patterns/retry.md +++ b/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) diff --git a/docs/reference-architectures/sharepoint/index.md b/docs/reference-architectures/sharepoint/index.md index 7ecd66d405d..e6c12c0816b 100644 --- a/docs/reference-architectures/sharepoint/index.md +++ b/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 diff --git a/docs/reference-architectures/virtual-machines-windows/single-vm.md b/docs/reference-architectures/virtual-machines-windows/single-vm.md index a2c5b899df5..ec960a4ca1a 100644 --- a/docs/reference-architectures/virtual-machines-windows/single-vm.md +++ b/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 diff --git a/docs/resiliency/disaster-recovery-azure-applications.md b/docs/resiliency/disaster-recovery-azure-applications.md index 55535ba55f0..42b51411104 100644 --- a/docs/resiliency/disaster-recovery-azure-applications.md +++ b/docs/resiliency/disaster-recovery-azure-applications.md @@ -264,7 +264,7 @@ As with the hybrid scenario, the failover deployments in the previous disaster r If your DR strategy relies upon multiple cloud platforms, it's valuable to include abstraction layers in the design of the solution. This eliminates the need to develop and maintain two different versions of the same application for different cloud platforms in case of disaster. As with the hybrid scenario, the use of Azure Virtual Machines or Azure Container Service might be easier in these cases than the use of cloud-specific PaaS designs. ## Automation -Some of the patterns that we just discussed require quick activation of offline deployments as well as restoration of specific parts of a system. Automation scripts can activate resources on demand and deploy solutions rapidly. The DR-related automation examples below use [Azure PowerShell](https://msdn.microsoft.com/library/azure/jj156055.aspx), but using the [Azure CLI](https://docs.microsoft.com/en-us/cli/azure/get-started-with-azure-cli) or the [Service Management REST API](https://msdn.microsoft.com/library/azure/ee460799.aspx) are also good options. +Some of the patterns that we just discussed require quick activation of offline deployments as well as restoration of specific parts of a system. Automation scripts can activate resources on demand and deploy solutions rapidly. The DR-related automation examples below use [Azure PowerShell](https://msdn.microsoft.com/library/azure/jj156055.aspx), but using the [Azure CLI](https://docs.microsoft.com/cli/azure/get-started-with-azure-cli) or the [Service Management REST API](https://msdn.microsoft.com/library/azure/ee460799.aspx) are also good options. Automation scripts manage aspects of DR not transparently handled by Azure. This produces consistent and repeatable results, minimizing human error. Predefined DR scripts also reduce the time to rebuild a system and its constituent parts during a disaster. You don’t want to try to manually figure out how to restore your site while it's down and losing money every minute. @@ -273,7 +273,7 @@ Test your scripts repeatedly from start to finish. After verifying their basic f A best practice with automation is to create a repository of PowerShell scripts or command-line interface (CLI) scripts for Azure disaster recovery. Clearly mark and categorize them for quick access. Designate a primary person to manage the repository and versioning of the scripts. Document them well with explanations of parameters and examples of script use. Also ensure that you keep this documentation in sync with your Azure deployments. This underscores the purpose of having a primary person in charge of all parts of the repository. ## Failure detection -To correctly handle problems with availability and disaster recovery, you must be able to detect and diagnose failures. Perform advanced server and deployment monitoring to quickly recognize when a system or its components suddenly become unavailable. Monitoring tools that assess the overall health of the cloud service and its dependencies can perform part of this work. One suitable Microsoft tool is [System Center 2016](https://www.microsoft.com/en-us/server-cloud/products/system-center-2016/). Third-party tools can also provide monitoring capabilities. Most monitoring solutions track key performance counters and service availability. +To correctly handle problems with availability and disaster recovery, you must be able to detect and diagnose failures. Perform advanced server and deployment monitoring to quickly recognize when a system or its components suddenly become unavailable. Monitoring tools that assess the overall health of the cloud service and its dependencies can perform part of this work. One suitable Microsoft tool is [System Center 2016](https://www.microsoft.com/server-cloud/products/system-center-2016/). Third-party tools can also provide monitoring capabilities. Most monitoring solutions track key performance counters and service availability. Although these tools are vital, you must plan for fault detection and reporting within a cloud service. You must also plan to properly use Azure Diagnostics. Custom performance counters or event-log entries can also be part of the overall strategy. This provides more data during failures to quickly diagnose the problem and restore full capabilities. It also provides additional metrics that the monitoring tools can use to determine application health. For more information, see [Enabling Azure Diagnostics in Azure Cloud Services](/azure/cloud-services/cloud-services-dotnet-diagnostics/). For a discussion of how to plan for an overall “health model,” see [Failsafe: Guidance for Resilient Cloud Architectures](https://channel9.msdn.com/Series/FailSafe). diff --git a/docs/resources/diagrams.md b/docs/resources/diagrams.md index ec03a192b2c..3544b71f242 100644 --- a/docs/resources/diagrams.md +++ b/docs/resources/diagrams.md @@ -14,7 +14,7 @@ The symbol/icon set is a collection of Visio, PowerPoint, PNG, and SVG assets th ![Cloud and Enterprise Symbol/Icon set](./_images/CnESymbols.png) -Additional symbols for Microsoft Office and related technologies are available in the [Microsoft Office Visio stencil](http://www.microsoft.com/en-us/download/details.aspx?id=35772). They are not optimized for architectural diagrams. +Additional symbols for Microsoft Office and related technologies are available in the [Microsoft Office Visio stencil](http://www.microsoft.com/download/details.aspx?id=35772). They are not optimized for architectural diagrams. > [!NOTE] > These assets are not intended for use in user interfaces. diff --git a/docs/service-fabric/migrate-from-cloud-services.md b/docs/service-fabric/migrate-from-cloud-services.md index 2699bf30ed8..59ecbe58636 100644 --- a/docs/service-fabric/migrate-from-cloud-services.md +++ b/docs/service-fabric/migrate-from-cloud-services.md @@ -222,7 +222,7 @@ As mentioned, the Kestrel web server requires a reverse proxy for security reaso ### Layer 7 routing -In the [original Surveys application](https://msdn.microsoft.com/en-us/library/hh534477.aspx#sec21), one web role listened on port 80, and the other web role listened on port 443. +In the [original Surveys application](https://msdn.microsoft.com/library/hh534477.aspx#sec21), one web role listened on port 80, and the other web role listened on port 443. | Public site | Survey management site | |-------------|------------------------| @@ -324,7 +324,7 @@ Now that the Surveys application has been successfully ported, Tailspin wants to [sf-reverse-proxy]: /azure/service-fabric/service-fabric-reverseproxy [sf-security]: /azure/service-fabric/service-fabric-cluster-security [sf-why-microservices]: /azure/service-fabric/service-fabric-overview-microservices -[tailspin-book]: https://msdn.microsoft.com/en-us/library/ff966499.aspx -[tailspin-scenario]: https://msdn.microsoft.com/en-us/library/hh534482.aspx -[unity]: https://msdn.microsoft.com/en-us/library/ff647202.aspx +[tailspin-book]: https://msdn.microsoft.com/library/ff966499.aspx +[tailspin-scenario]: https://msdn.microsoft.com/library/hh534482.aspx +[unity]: https://msdn.microsoft.com/library/ff647202.aspx [vm-scale-sets]: /azure/virtual-machine-scale-sets/virtual-machine-scale-sets-overview diff --git a/docs/service-fabric/refactor-migrated-app.md b/docs/service-fabric/refactor-migrated-app.md index e765f07f3e0..a1b2799f086 100644 --- a/docs/service-fabric/refactor-migrated-app.md +++ b/docs/service-fabric/refactor-migrated-app.md @@ -146,7 +146,7 @@ The Surveys application code is available on [GitHub][sample-code]. If you are just getting started with [Azure Service Fabric][service-fabric], first set up your development environment then download the latest [Azure SDK][azure-sdk] and the [Azure Service Fabric SDK][service-fabric-sdk]. The SDK includes the OneBox cluster manager so you can deploy and test the Surveys application locally with full F5 debugging. -[azure-sdk]: https://azure.microsoft.com/en-us/downloads/archive-net-downloads/ +[azure-sdk]: https://azure.microsoft.com/downloads/archive-net-downloads/ [container-scenarios]: /azure/service-fabric/service-fabric-containers-overview [kestrel]: https://docs.microsoft.com/aspnet/core/fundamentals/servers/kestrel?tabs=aspnetcore2x [kestrel-intro]: https://docs.microsoft.com/aspnet/core/fundamentals/servers/kestrel?tabs=aspnetcore1x