fix broken links

cephalin · cephalin · commit 9da005ed66e5 · 2023-01-09T17:08:22.000+01:00
diff --git a/articles/app-service/app-service-web-tutorial-custom-domain.md b/articles/app-service/app-service-web-tutorial-custom-domain.md
@@ -36,7 +36,7 @@ The DNS record type you need to add with your domain provider depends on the dom
 1. In the left menu for your app, select **Custom domains**.
 1. Select **Add custom domain**.
 
-    :::image type="content" source="./media/app-service-web-tutorial-custom-domain/add-custom-domain.png" alt-text="A screenshot showing how to configure a new custom domain, along with a managed certificate.":::
+    :::image type="content" source="./media/app-service-web-tutorial-custom-domain/add-custom-domain.png" alt-text="A screenshot showing how to open the Add custom domain dialog.":::
 
 1. For **Domain provider**, select **All other domain services** to configure a third-party domain.
 
@@ -164,7 +164,10 @@ Browse to the DNS names that you configured earlier.
 
 <a name="resolve-404-not-found" aria-hidden="true"></a>
 
-If you receive an HTTP 404 (Not Found) error when you browse to the URL of your custom domain, most likely the browser client has cached the old IP address of your domain. Clear the cache, and test DNS resolution again. On a Windows machine, you clear the cache with `ipconfig /flushdns`.
+If you receive an HTTP 404 (Not Found) error when you browse to the URL of your custom domain, the two most-likely causes are:
+
+- The browser client has cached the old IP address of your domain. Clear the cache, and test DNS resolution again. On a Windows machine, you clear the cache with `ipconfig /flushdns`.
+- You configured an IP-based certificate binding, and the app's IP address has changed because of it. [Remap the A record](configure-ssl-bindings.md#remap-records-for-ip-ssl) in your DNS entries to the new IP address.
 
 If you receive a `Page not secure` warning or error, it's because your domain doesn't have a certificate binding yet. [Add a private certificate for the domain](configure-ssl-certificate.md) and [configure the binding](configure-ssl-bindings.md).
 
diff --git a/articles/app-service/configure-domain-traffic-manager.md b/articles/app-service/configure-domain-traffic-manager.md
@@ -73,7 +73,7 @@ Once you have finished adding or modifying DNS records at your domain provider,
 
 Since Traffic Manager only supports custom domain mapping with CNAME records, and because DNS standards don't support CNAME records for mapping root domains (for example, **contoso.com**), Traffic Manager doesn't support mapping to root domains. To work around this issue, use a URL redirect from at the app level. In ASP.NET Core, for example, you can use [URL Rewriting](/aspnet/core/fundamentals/url-rewriting). Then, use Traffic Manager to load balance the subdomain (**www.contoso.com**). Another approach is you can [create an alias record for your domain name apex to reference an Azure Traffic Manager profile](../dns/tutorial-alias-tm.md). An example is contoso.com. Instead of using a redirecting service, you can configure Azure DNS to reference a Traffic Manager profile directly from your zone. 
 
-For high availability scenarios, you can implement a load-balancing DNS setup without Traffic Manager by creating multiple *A records* that point from the root domain to each app copy's IP address. Then, [map the same root domain to all the app copies](app-service-web-tutorial-custom-domain.md#3-create-the-dns-records). Since the same domain name cannot be mapped to two different apps in the same region, this setup only works when your app copies are in different regions.
+For high availability scenarios, you can implement a load-balancing DNS setup without Traffic Manager by creating multiple *A records* that point from the root domain to each app copy's IP address. Then, [map the same root domain to all the app copies](app-service-web-tutorial-custom-domain.md#2-create-the-dns-records). Since the same domain name cannot be mapped to two different apps in the same region, this setup only works when your app copies are in different regions.
 
 ## Enable custom domain
 After the records for your domain name have propagated, use the browser to verify that your custom domain name resolves to your App Service app.
diff --git a/articles/app-service/configure-ssl-bindings.md b/articles/app-service/configure-ssl-bindings.md
@@ -83,9 +83,9 @@ There are two changes you need to make, potentially:
 
 - By default, your app uses a shared public IP address. When you bind a certificate with IP SSL, App Service creates a new, dedicated IP address for your app. If you mapped an A record to your app, update your domain registry with this new, dedicated IP address.
 
-    Your app's **Custom domain** page is updated with the new, dedicated IP address. [Copy this IP address](app-service-web-tutorial-custom-domain.md#info), then [remap the A record](app-service-web-tutorial-custom-domain.md#3-create-the-dns-records) to this new IP address.
+    Your app's **Custom domain** page is updated with the new, dedicated IP address. Copy this IP address, then [remap the A record](app-service-web-tutorial-custom-domain.md#2-create-the-dns-records) to this new IP address.
 
-- If you have an SNI SSL binding to `<app-name>.azurewebsites.net`, [remap any CNAME mapping](app-service-web-tutorial-custom-domain.md#3-create-the-dns-records) to point to `sni.<app-name>.azurewebsites.net` instead (add the `sni` prefix).
+- If you have an SNI SSL binding to `<app-name>.azurewebsites.net`, [remap any CNAME mapping](app-service-web-tutorial-custom-domain.md#2-create-the-dns-records) to point to `sni.<app-name>.azurewebsites.net` instead (add the `sni` prefix).
 
 ## Test HTTPS
 
diff --git a/articles/app-service/includes/quickstart-custom-container/quickstart-custom-container-linux-azure-portal-pivot.md b/articles/app-service/includes/quickstart-custom-container/quickstart-custom-container-linux-azure-portal-pivot.md
@@ -121,7 +121,7 @@ Congratulations, you've successfully completed this quickstart.
 The App Service app pulls from the container registry every time it starts. If you rebuild your image, you just need to push it to your container registry, and the app pulls in the updated image when it restarts. To tell your app to pull in the updated image immediately, restart it.
 
 > [!div class="nextstepaction"]
-> [Secure with custom domain and certificate](tutorial-secure-domain-certificate.md)
+> [Secure with custom domain and certificate](../../tutorial-secure-domain-certificate.md)
 
 > [!div class="nextstepaction"]
 > [Configure custom container](../../configure-custom-container.md)
diff --git a/articles/app-service/includes/quickstart-custom-container/quickstart-custom-container-linux-visual-studio-code-pivot.md b/articles/app-service/includes/quickstart-custom-container/quickstart-custom-container-linux-visual-studio-code-pivot.md
@@ -163,7 +163,7 @@ Congratulations, you've successfully completed this quickstart.
 The App Service app pulls from the container registry every time it starts. If you rebuild your image, you just need to push it to your container registry, and the app pulls in the updated image when it restarts. To tell your app to pull in the updated image immediately, restart it.
 
 > [!div class="nextstepaction"]
-> [Secure with custom domain and certificate](tutorial-secure-domain-certificate.md)
+> [Secure with custom domain and certificate](../../tutorial-secure-domain-certificate.md)
 
 > [!div class="nextstepaction"]
 > [Configure custom container](../../configure-custom-container.md)
diff --git a/articles/app-service/includes/quickstart-custom-container/quickstart-custom-container-windows-azure-portal-pivot.md b/articles/app-service/includes/quickstart-custom-container/quickstart-custom-container-windows-azure-portal-pivot.md
@@ -125,7 +125,7 @@ Congratulations, you've successfully completed this quickstart.
 The App Service app pulls from the container registry every time it starts. If you rebuild your image, you just need to push it to your container registry, and the app pulls in the updated image when it restarts. To tell your app to pull in the updated image immediately, restart it.
 
 > [!div class="nextstepaction"]
-> [Secure with custom domain and certificate](tutorial-secure-domain-certificate.md)
+> [Secure with custom domain and certificate](../../tutorial-secure-domain-certificate.md)
 
 > [!div class="nextstepaction"]
 > [Configure custom container](../../configure-custom-container.md)
diff --git a/articles/app-service/includes/quickstart-custom-container/quickstart-custom-container-windows-cli-pivot.md b/articles/app-service/includes/quickstart-custom-container/quickstart-custom-container-windows-cli-pivot.md
@@ -83,7 +83,7 @@ Congratulations, you've successfully completed this quickstart.
 The App Service app pulls from the container registry every time it starts. If you rebuild your image, you just need to push it to your container registry, and the app pulls in the updated image when it restarts. To tell your app to pull in the updated image immediately, restart it.
 
 > [!div class="nextstepaction"]
-> [Secure with custom domain and certificate](tutorial-secure-domain-certificate.md)
+> [Secure with custom domain and certificate](../../tutorial-secure-domain-certificate.md)
 
 > [!div class="nextstepaction"]
 > [Configure custom container](../../configure-custom-container.md)
diff --git a/articles/app-service/includes/quickstart-custom-container/quickstart-custom-container-windows-powershell-pivot.md b/articles/app-service/includes/quickstart-custom-container/quickstart-custom-container-windows-powershell-pivot.md
@@ -83,7 +83,7 @@ Congratulations, you've successfully completed this quickstart.
 The App Service app pulls from the container registry every time it starts. If you rebuild your image, you just need to push it to your container registry, and the app pulls in the updated image when it restarts. To tell your app to pull in the updated image immediately, restart it.
 
 > [!div class="nextstepaction"]
-> [Secure with custom domain and certificate](tutorial-secure-domain-certificate.md)
+> [Secure with custom domain and certificate](../../tutorial-secure-domain-certificate.md)
 
 > [!div class="nextstepaction"]
 > [Configure custom container](../../configure-custom-container.md)
diff --git a/articles/app-service/includes/quickstart-custom-container/quickstart-custom-container-windows-visual-studio-pivot.md b/articles/app-service/includes/quickstart-custom-container/quickstart-custom-container-windows-visual-studio-pivot.md
@@ -172,7 +172,7 @@ The streamed logs look like this:
 ## Next steps
 
 > [!div class="nextstepaction"]
-> [Secure with custom domain and certificate](tutorial-secure-domain-certificate.md)
+> [Secure with custom domain and certificate](../../tutorial-secure-domain-certificate.md)
 
 > [!div class="nextstepaction"]
 > [Migrate to Windows container in Azure](../../tutorial-custom-container.md)
diff --git a/articles/app-service/manage-custom-dns-migrate-domain.md b/articles/app-service/manage-custom-dns-migrate-domain.md
@@ -35,17 +35,17 @@ When you finally migrate your custom DNS name from the old site to the App Servi
 
 ### Get domain verification ID
 
-Get the domain verification ID for you app by following the steps at [Get domain verification ID](app-service-web-tutorial-custom-domain.md#2-get-a-domain-verification-id).
+Get the domain verification ID for you app by following the steps at [Configure a custom domain](app-service-web-tutorial-custom-domain.md#1-configure-a-custom-domain).
 
 ### Create domain verification record
 
 To verify domain ownership, add a TXT record for domain verification. The hostname for the TXT record depends on the type of DNS record type you want to map. See the following table (`@` typically represents the root domain):
 
 | DNS record example | TXT Host | TXT Value |
 | - | - | - |
-| \@ (root) | _asuid_ | [Domain verification ID for your app](app-service-web-tutorial-custom-domain.md#2-get-a-domain-verification-id) |
-| www (sub) | _asuid.www_ | [Domain verification ID for your app](app-service-web-tutorial-custom-domain.md#2-get-a-domain-verification-id) |
-| \* (wildcard) | _asuid_ | [Domain verification ID for your app](app-service-web-tutorial-custom-domain.md#2-get-a-domain-verification-id) |
+| \@ (root) | _asuid_ | Domain verification ID shown in the **Add custom domain** dialog. |
+| www (sub) | _asuid.www_ | Domain verification ID shown in the **Add custom domain** dialog. |
+| \* (wildcard) | _asuid_ | Domain verification ID shown in the **Add custom domain** dialog. |
 
 In your DNS records page, note the record type of the DNS name you want to migrate. App Service supports mappings from CNAME and A records.
 
diff --git a/articles/app-service/media/app-service-web-tutorial-custom-domain/add-custom-domain-complete.png b/articles/app-service/media/app-service-web-tutorial-custom-domain/add-custom-domain-complete.png
diff --git a/articles/app-service/media/app-service-web-tutorial-custom-domain/configure-custom-domain-add.png b/articles/app-service/media/app-service-web-tutorial-custom-domain/configure-custom-domain-add.png
diff --git a/articles/app-service/troubleshoot-domain-ssl-certificates.md b/articles/app-service/troubleshoot-domain-ssl-certificates.md
@@ -116,7 +116,7 @@ Your configured custom domain is missing a "CNAME record" or an "A record".
 
 **Solution for cause 1**
 
-- If you added an "A record", make sure that a TXT record is also added. For more information, see [Create the "A record"](./app-service-web-tutorial-custom-domain.md).
+- If you added an "A record", make sure that a TXT record is also added. For more information, see [Create the DNS records](./app-service-web-tutorial-custom-domain.md#2-create-the-dns-records).
 
 - If you don't have to use the root domain for your app, the recommendation is that you use a "CNAME record", rather than an "A record".
 
diff --git a/articles/app-service/tutorial-custom-container.md b/articles/app-service/tutorial-custom-container.md
@@ -1088,7 +1088,7 @@ What you learned:
 
 ::: zone-end
 
-In the next tutorial, you learn how to map a custom DNS name to your app.
+In the next tutorial, you learn how to secure your app with a custom domain and certificate.
 
 > [!div class="nextstepaction"]
 > [Secure with custom domain and certificate](tutorial-secure-domain-certificate.md)
diff --git a/articles/security/fundamentals/subdomain-takeover.md b/articles/security/fundamentals/subdomain-takeover.md
@@ -226,6 +226,6 @@ To learn more about related services and Azure features you can use to defend ag
 
 - [Prevent dangling DNS records with Azure DNS](../../dns/dns-alias.md#prevent-dangling-dns-records)
 
-- [Use a domain verification ID when adding custom domains in Azure App Service](../../app-service/app-service-web-tutorial-custom-domain.md#2-get-a-domain-verification-id)
+- [Use a domain verification ID when adding custom domains in Azure App Service](../../app-service/app-service-web-tutorial-custom-domain.md#1-configure-a-custom-domain)
 
 - [Quickstart: Run your first Resource Graph query using Azure PowerShell](../../governance/resource-graph/first-query-powershell.md)
diff --git a/includes/app-service-ssl-binding-types.md b/includes/app-service-ssl-binding-types.md
@@ -14,5 +14,5 @@ ms.custom: "include file"
 |-|-|
 | Custom domain | The domain name to add the TLS/SSL binding for. |
 | Private Certificate Thumbprint | The certificate to bind. |
-| TLS/SSL Type | <ul><li>**[SNI SSL](https://en.wikipedia.org/wiki/Server_Name_Indication)** - Multiple SNI SSL bindings may be added. This option allows multiple TLS/SSL certificates to secure multiple domains on the same IP address. Most modern browsers (including Internet Explorer, Chrome, Firefox, and Opera) support SNI (for more information, see [Server Name Indication](https://wikipedia.org/wiki/Server_Name_Indication)).</li><li>**IP SSL** - Only one IP SSL binding may be added. This option allows only one TLS/SSL certificate to secure a dedicated public IP address. After you configure the binding, follow the steps in [Remap records for IP SSL](#remap-records-for-ip-ssl).<br/>IP SSL is supported only in **Standard** tier or above. </li></ul> |
+| TLS/SSL Type | <ul><li>**[SNI SSL](https://en.wikipedia.org/wiki/Server_Name_Indication)** - Multiple SNI SSL bindings may be added. This option allows multiple TLS/SSL certificates to secure multiple domains on the same IP address. Most modern browsers (including Internet Explorer, Chrome, Firefox, and Opera) support SNI (for more information, see [Server Name Indication](https://wikipedia.org/wiki/Server_Name_Indication)).</li><li>**IP SSL** - Only one IP SSL binding may be added. This option allows only one TLS/SSL certificate to secure a dedicated public IP address. After you configure the binding, follow the steps in [Remap records for IP SSL](../articles/app-service/configure-ssl-bindings.md#remap-records-for-ip-ssl).<br/>IP SSL is supported only in **Standard** tier or above. </li></ul> |
 
