Merge pull request #205588 from rboucher/ServHealthPageChange

New service health updates

Author: 19BMG00

articles/active-directory-b2c/best-practices.md

@@ -87,4 +87,4 @@ Stay up to date with the state of the service and find support options.
 |--|--|
 | [Service updates](https://azure.microsoft.com/updates/?product=active-directory-b2c) |  Stay up to date with Azure AD B2C product updates and announcements. |
 | [Microsoft Support](support-options.md) | File a support request for Azure AD B2C technical issues. Billing and subscription management support is provided at no cost. |
-| [Azure status](https://status.azure.com/status) | View the current health status of all Azure services. |
+| [Azure status](https://azure.status.microsoft/status) | View the current health status of all Azure services. |

articles/active-directory/reports-monitoring/reference-azure-ad-sla-performance.md

@@ -80,7 +80,7 @@ The numbers above are a global total of Azure AD authentications across all cust
 
 ## Incident history 
 
-All incidents that seriously impact Azure AD performance are documented in the [Azure status history](https://status.azure.com/status/history/). Not all events documented in Azure status history are serious enough to cause Azure AD to go below its SLA. You can view information about the impact of incidents, as well as a root cause analysis of what caused the incident and what steps Microsoft took to prevent future incidents. 
+All incidents that seriously impact Azure AD performance are documented in the [Azure status history](https://azure.status.microsoft/status/history/). Not all events documented in Azure status history are serious enough to cause Azure AD to go below its SLA. You can view information about the impact of incidents, as well as a root cause analysis of what caused the incident and what steps Microsoft took to prevent future incidents. 
 
 
 

articles/analysis-services/TOC.yml

@@ -129,7 +129,7 @@
   - name: Azure updates
     href: https://azure.microsoft.com/updates/?query=Analysis%20Services
   - name: Azure status
-    href: https://status.azure.com/
+    href: https://azure.status.microsoft/
   - name: Feedback
     href: https://feedback.azure.com/d365community/forum/d92323a0-0525-ec11-b6e6-000d3a4f0858
   - name: Pricing

articles/api-management/vscode-create-service-instance.md

@@ -47,7 +47,7 @@ In the pane that opens, supply a name for the new API Management instance. It mu
 A new API Management instance (and parent resource group) will be created with the specified name. By default, the instance is created in the *West US* region with *Consumption* SKU.
 
 > [!TIP]
-> If you enable **Advanced Creation** in the *Azure API Management Extension Settings*, you can also specify an [API Management SKU](https://azure.microsoft.com/pricing/details/api-management/), [Azure region](https://status.azure.com/en-us/status), and a [resource group](../azure-resource-manager/management/overview.md) to deploy your API Management instance.
+> If you enable **Advanced Creation** in the *Azure API Management Extension Settings*, you can also specify an [API Management SKU](https://azure.microsoft.com/pricing/details/api-management/), [Azure region](https://azure.status.microsoft/en-us/status), and a [resource group](../azure-resource-manager/management/overview.md) to deploy your API Management instance.
 >
 > While the *Consumption* SKU takes less than a minute to set up, other SKUs typically take 30-40 minutes to create.
 

articles/azure-portal/azure-portal-safelist-urls.md

@@ -108,7 +108,7 @@ servicebus.azure.net (Azure Service Bus)
 servicebus.windows.net (Azure Service Bus)
 shell.azure.com (Azure Command Shell)
 sphere.azure.net (Azure Sphere)
-status.azure.com (Azure Status)
+azure.status.microsoft (Azure Status)
 storage.azure.com (Azure Storage)
 storage.azure.net (Azure Storage)
 vault.azure.net (Azure Key Vault Service)

articles/cosmos-db/sql/troubleshoot-service-unavailable-java-sdk-v4-sql.md

@@ -49,7 +49,7 @@ Follow the [request timeout troubleshooting steps](troubleshoot-request-timeout-
 UnknownHostException means that the Java framework cannot resolve the DNS entry for the Cosmos DB endpoint in the affected machine. You should verify that the machine can resolve the DNS entry or if you have any custom DNS resolution software (such as VPN or Proxy, or a custom solution), make sure it contains the right configuration for the DNS endpoint that the error is claiming cannot be resolved. If the error is constant, you can verify the machine's DNS resolution through a `curl` command to the endpoint described in the error.
 
 ### Service outage
-Check the [Azure status](https://status.azure.com/status) to see if there's an ongoing issue.
+Check the [Azure status](https://azure.status.microsoft/status) to see if there's an ongoing issue.
 
 
 ## Next steps

articles/cosmos-db/sql/troubleshoot-service-unavailable.md

@@ -32,7 +32,7 @@ TransportException: A client transport error occurred: The request timed out whi
 Follow the [request timeout troubleshooting steps](troubleshoot-dot-net-sdk-request-timeout.md#troubleshooting-steps) to resolve it.
 
 ### Service outage
-Check the [Azure status](https://status.azure.com/status) to see if there's an ongoing issue.
+Check the [Azure status](https://azure.status.microsoft/status) to see if there's an ongoing issue.
 
 
 ## Next steps

articles/digital-twins/how-to-monitor-resource-health.md

@@ -50,7 +50,7 @@ For more information on using Azure Service Health, see [Service Health overview
 
 The [Azure status](../service-health/azure-status-overview.md) page provides a global view of the health of Azure services and regions. While Azure Service Health and Azure Resource Health are personalized to your specific resource, Azure status has a larger scope and can be useful to understand incidents with wide-ranging impact.
 
-To check Azure status, navigate to the [Azure status](https://status.azure.com/status/) page. The page displays a table of Azure services along with health indicators per region. You can view Azure Digital Twins by searching for its table entry on the page.
+To check Azure status, navigate to the [Azure status](https://azure.status.microsoft/status/) page. The page displays a table of Azure services along with health indicators per region. You can view Azure Digital Twins by searching for its table entry on the page.
 
 For more information on using the Azure status page, see [Azure status overview](../service-health/azure-status-overview.md).
 

articles/hdinsight/create-cluster-error-dictionary.md

@@ -193,7 +193,7 @@ Typically, this error is generated when there's a transient problem or an Azure
 
 ### Resolution
 
-Check the [Azure status](https://status.azure.com) page for any Azure outages that might affect cluster deployment. If there are no outages, retry cluster deployment.
+Check the [Azure status](https://azure.status.microsoft) page for any Azure outages that might affect cluster deployment. If there are no outages, retry cluster deployment.
 
 ---
 

articles/hdinsight/hadoop/hdinsight-troubleshoot-cluster-creation-fails.md

@@ -71,7 +71,7 @@ Other naming restrictions also apply for cluster creation. See [Cluster name res
 
 ## Service outages
 
-Check [Azure status](https://status.azure.com) for any potential outages or service issues.
+Check [Azure status](https://azure.status.microsoft) for any potential outages or service issues.
 
 ## Next steps