Merge pull request #301832 from MicrosoftDocs/main

Merged by Learn.Build PR Management system

Author: learn-build-service-prod[bot]

articles/api-management/send-one-way-request-policy.md

@@ -57,6 +57,10 @@ The `send-one-way-request` policy sends the provided request to the specified UR
 - [**Policy scopes:**](./api-management-howto-policies.md#scopes) global, workspace, product, API, operation
 -  [**Gateways:**](api-management-gateways-overview.md) classic, v2, consumption, self-hosted
 
+### Usage notes
+
+* Using multiple `send-one-way-request` policies in outbound section is not supported in self-hosted gateway.
+
 ## Example
 
 This example uses the `send-one-way-request` policy to send a message to a Slack chat room if the HTTP response code is greater than or equal to 500. For more information on this sample, see [Using external services from the Azure API Management service](./api-management-sample-send-request.md).
@@ -91,4 +95,4 @@ This example uses the `send-one-way-request` policy to send a message to a Slack
 
 * [Integration and external communication](api-management-policies.md#integration-and-external-communication)
 
-[!INCLUDE [api-management-policy-ref-next-steps](../../includes/api-management-policy-ref-next-steps.md)]
+[!INCLUDE [api-management-policy-ref-next-steps](../../includes/api-management-policy-ref-next-steps.md)]

articles/frontdoor/refstring.md

@@ -1,5 +1,6 @@
 ---
-title: Troubleshooting 4xx and 5xx erorrs using Reference String 
+title: Troubleshoot 4xx and 5xx Errors Using Reference String
+titleSuffix: Azure Front Door
 description: This article provides information about what a Reference String is, how to collect them, and use the Azure portal diagnostic tool for troubleshooting 4xx and 5xx errors.
 author: Alej-b23 
 ms.author: pagonzalez 
@@ -10,13 +11,13 @@ ms.date: 12/03/2024
 #CustomerIntent: As a web developer, I want troubleshoot my web application using a Reference String.
 ---
 
-# Troubleshooting 4xx and 5xx errors using Reference String
+# Troubleshoot 4xx and 5xx errors using Reference String
 
 A guide to understand and use Reference Strings for diagnosing and resolving issues with Azure Front Door.
 
 ## Prerequisites
 
-* You must have an Azure Front Door profile. To create a profile, see [Creating an Azure Front Door profile](create-front-door-portal.md).
+* You must have an Azure Front Door profile. To create a profile, see [Create an Azure Front Door profile](create-front-door-portal.md).
 
 ## What is a Reference String?
 
@@ -90,4 +91,4 @@ For more information on tracking references and access log parameters, see [Moni
 ## Next steps
 
 * To learn more about navigating common issues, see [Front Door Troubleshooting Issues](troubleshoot-issues.md). 
-* For answers to common questions, see [Azure Front Door FAQ](front-door-faq.yml).
+* For answers to common questions, see [Azure Front Door FAQ](front-door-faq.yml).

articles/frontdoor/scenario-storage-blobs.md

@@ -18,7 +18,7 @@ Azure Front Door enhances the delivery of static content from Azure Storage blob
 
 In this reference architecture, a storage account and an Azure Front Door profile with a single origin are deployed.
 
-## Dataflow
+## Data flow
 
 The data flows through the scenario as follows:
 
@@ -40,7 +40,7 @@ The data flows through the scenario as follows:
 
 If you store static files with another cloud storage provider or on your own infrastructure, this scenario still largely applies. However, you need to ensure that incoming traffic to your origin server is verified to come through Front Door. If your storage provider doesn't support Private Link, consider using an alternative approach like [allowlisting the Front Door service tag and inspecting the `X-Azure-FDID` header](origin-security.md).
 
-## Scenario Details
+## Scenario details
 
 Static content delivery is beneficial in many situations, such as:
 - Delivering images, CSS files, and JavaScript files for a web application.
@@ -53,7 +53,7 @@ In complex scenarios, a single Front Door profile can serve both static and dyna
 
 ## Considerations
 
-### Scalability and Performance
+### Scalability and performance
 
 Azure Front Door acts as a content delivery network (CDN), caching content at its globally distributed PoPs. When a cached response is available, Azure Front Door quickly serves it, enhancing performance and reducing the load on the origin. If the PoP lacks a valid cached response, Azure Front Door's traffic acceleration capabilities expedite content delivery from the origin.
 
@@ -63,12 +63,12 @@ Azure Front Door acts as a content delivery network (CDN), caching content at it
 
 Azure Front Door is designed for internet-facing scenarios and is optimized for publicly accessible blobs. To authenticate access to blobs, consider using [shared access signatures (SAS)](../storage/common/storage-sas-overview.md). Ensure you enable the [*Use Query String* behavior](front-door-caching.md#query-string-behavior) to prevent Azure Front Door from serving requests to unauthenticated clients. This approach might limit the effectiveness of caching, as each request with a different SAS must be sent to the origin.
 
-#### Origin Security
+#### Origin security
 
-- If you are using the premium tier, Azure Front Door can connect securely to the Azure Storage account using [Private Link](private-link.md). The storage account can be configured to deny public network access, allowing requests only through the private endpoint used by Azure Front Door. This setup ensures all requests get processed by Azure Front Door, protecting your storage account from direct internet exposure. 
-- If you are using the standard tier, you can secure requests with a [shared access signature (SAS)](../storage/common/storage-sas-overview.md) and either have clients include the SAS in their requests or use the Azure Front Door [rules engine](front-door-rules-engine.md) to attach it. Note that the storage account's network access must be publicly accessible (from all networks or from Front Door IP addresses in AzureFrontDoor.Backend service tag).
+- If you're using the premium tier, Azure Front Door can connect securely to the Azure Storage account using [Private Link](private-link.md). The storage account can be configured to deny public network access, allowing requests only through the private endpoint used by Azure Front Door. This setup ensures all requests get processed by Azure Front Door, protecting your storage account from direct internet exposure. 
+- If you're using the standard tier, you can secure requests with a [shared access signature (SAS)](../storage/common/storage-sas-overview.md) and either have clients include the SAS in their requests or use the Azure Front Door [rules engine](front-door-rules-engine.md) to attach it. The storage account's network access must be publicly accessible (from all networks or from Front Door IP addresses in `AzureFrontDoor.Backend` service tag).
 
-#### Custom Domain Names
+#### Custom domain names
 
 Azure Front Door supports custom domain names and can manage TLS certificates for these domains. Using custom domains ensures clients receive files from a trusted source, with TLS encrypting every connection to Azure Front Door. Azure Front Door's management of TLS certificates helps avoid outages and security issues from invalid or outdated certificates.
 
@@ -86,18 +86,18 @@ Using the Azure Front Door cache reduces the load on your storage account. If yo
 
 To further improve resiliency, consider the redundancy of your storage account. For more information, see [Azure Storage redundancy](../storage/common/storage-redundancy.md). Alternatively, deploy multiple storage accounts and configure multiple origins in your Azure Front Door origin group. Set up fail over between origins by configuring each origin's priority. For more information, see [Origins and origin groups in Azure Front Door](origin.md).
 
-### Cost Optimization
+### Cost optimization
 
 Caching helps reduce the cost of delivering static content. Azure Front Door's PoPs store copies of responses and can deliver these cached responses for subsequent requests, reducing the request load on the origin. In high-scale static content solutions, especially those delivering large files, caching can significantly reduce traffic costs.
 
 To use Private Link in this solution, deploy the premium tier of Azure Front Door. The standard tier can be used if you don't need to block direct traffic to your storage account. For more information, see [Origin security](#origin-security).
 
-## Deploy This Scenario
+## Deploy this scenario
 
 To deploy this scenario using Bicep or JSON ARM templates, [see this quickstart](https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.cdn/front-door-premium-storage-blobs-private-link).
 
 To deploy this scenario using Terraform, [see this quickstart](https://github.com/Azure/terraform/tree/master/quickstart/101-front-door-premium-storage-blobs-private-link).
 
-## Next Steps
+## Next step
 
 Learn how to [create an Azure Front Door profile](create-front-door-portal.md).

articles/frontdoor/scenarios.md

@@ -1,10 +1,10 @@
 ---
-title: Accelerate and secure your web application with Azure Front Door
+title: Accelerate and Secure Your Web Application with Azure Front Door
 description: This article explains how Front Door can help you to build a well architected solution on Azure.
 author: johndowns
 ms.author: jodowns
 ms.service: azure-frontdoor
-ms.topic: conceptual
+ms.topic: concept-article
 ms.date: 02/13/2023
 ---
 

articles/frontdoor/standard-premium/front-door-add-rules-cli.md

@@ -4,7 +4,7 @@ description: Learn how to create an Azure Front Door Standard/Premium with the A
 author: halkazwini
 ms.author: halkazwini
 ms.service: azure-frontdoor
-ms.topic: sample
+ms.topic: tutorial
 ms.date: 12/30/2021
 ms.custom: devx-track-azurecli
 ---
@@ -225,9 +225,9 @@ az afd security-policy create \
 
 When you create the Azure Front Door Standard/Premium profile, it takes a few minutes for the configuration to be deployed globally. Once completed, you can access the frontend host you created. In a browser, go to `contoso-frontend.z01.azurefd.net`. Your request will automatically get routed to the nearest server from the specified servers in the origin group.
 
-To test instant global failover, we'll use the following steps:
+To test instant global failover, use the following steps:
 
-1. Open a browser, as described above, and go to the frontend address: `contoso-frontend.azurefd.net`.
+1. Open a browser, and go to the frontend address: `contoso-frontend.azurefd.net`.
 
 2. In the Azure portal, search for and select *App services*. Scroll down to find one of your web apps, **WebAppContoso-1** in this example.
 

articles/frontdoor/standard-premium/subscription-offers.md

@@ -1,21 +1,22 @@
 ---
-title: Azure Front Door Standard/Premium subscription offers and bandwidth throttling
+title: Standard/Premium Subscription Offers and Bandwidth Throttling
+titleSuffix: Azure Front Door
 description: Learn about Azure Front Door Standard/Premium availability for a specific subscription type.
 author: halkazwini
 ms.author: halkazwini
 manager: kumud
 ms.service: azure-frontdoor
-ms.topic: troubleshooting
+ms.topic: troubleshooting-general
 ms.date: 11/18/2024
 ---
 
-# Azure Front Door Standard/Premium Subscription Offers and Bandwidth Throttling
+# Azure Front Door Standard/Premium subscription offers and bandwidth throttling
 
 **Applies to:** :heavy_check_mark: Front Door Standard :heavy_check_mark: Front Door Premium
 
 Azure Front Door Standard/Premium profiles are subject to bandwidth throttling based on your subscription type.
 
-## Free and Trial Subscriptions
+## Free and trial subscriptions
 
 Bandwidth throttling is applied to these subscription types.
 
@@ -25,11 +26,11 @@ Bandwidth is throttled until the subscription is verified to be in good standing
 
 If throttling persists after payment, you can request removal by [contacting support](https://portal.azure.com/?#blade/Microsoft_Azure_Support/HelpAndSupportBlade).
 
-## Enterprise Agreements
+## Enterprise agreements
 
 Refer to the bandwidth limits in [Azure Front Door limits](../../azure-resource-manager/management/azure-subscription-service-limits.md#azure-front-door-standard-and-premium-service-limits).
 
-## Other Offer Types
+## Other offer types
 
 The same rules as Pay-as-you-go apply to these subscription types:
 
@@ -38,6 +39,6 @@ The same rules as Pay-as-you-go apply to these subscription types:
 - Students
 - CSP
 
-## Next Steps
+## Next step
 
 Learn how to [create an Azure Front Door Standard/Premium profile](create-front-door-portal.md).

articles/frontdoor/standard-premium/troubleshoot-compression.md

@@ -1,5 +1,6 @@
 ---
-title: Troubleshooting file compression in Azure Front Door
+title: Troubleshoot File Compression
+titleSuffix: Azure Front Door
 description: Learn how to troubleshoot issues with file compression in Azure Front Door. This article covers several possible causes.
 author: halkazwini
 ms.author: halkazwini
@@ -8,7 +9,7 @@ ms.topic: how-to
 ms.date: 11/18/2024
 ---
 
-# Troubleshooting Azure Front Door file compression
+# Troubleshoot Azure Front Door file compression
 
 **Applies to:** :heavy_check_mark: Front Door Standard :heavy_check_mark: Front Door Premium
 

articles/frontdoor/standard-premium/troubleshoot-cross-origin-resources.md

@@ -1,10 +1,10 @@
 ---
-title: Using Azure Front Door Standard/Premium with Cross-Origin Resource Sharing
+title: Using Azure Front Door with Cross-Origin Resource Sharing
 description: Learn how to use the Azure Front Door (AFD) to with Cross-Origin Resource Sharing (CORS).
 author: halkazwini
 ms.author: qixwang
 ms.service: azure-frontdoor
-ms.topic: how-to
+ms.topic: concept-article
 ms.date: 12/28/2023
 ---
 
@@ -14,7 +14,7 @@ ms.date: 12/28/2023
 
 ## What is CORS?
 
-CORS (Cross Origin Resource Sharing) is an HTTP feature that enables a web application running under one domain to access resources in another domain. To reduce the possibility of cross-site scripting attacks, all modern web browsers implement a security restriction known as [same-origin policy](https://www.w3.org/Security/wiki/Same_Origin_Policy). This prevents a web page from calling APIs in a different domain.  CORS provides a secure way to allow one origin (the origin domain) to call APIs in another origin.
+CORS (Cross Origin Resource Sharing) is an HTTP feature that enables a web application running under one domain to access resources in another domain. To reduce the possibility of cross-site scripting attacks, all modern web browsers implement a security restriction known as [same-origin policy](https://www.w3.org/Security/wiki/Same_Origin_Policy). This prevents a web page from calling APIs in a different domain. CORS provides a secure way to allow one origin (the origin domain) to call APIs in another origin.
 
 ## How it works
 
@@ -48,12 +48,12 @@ A complex request is a CORS request where the browser is required to send a *pre
 >
 
 ## Wildcard or single origin scenarios
-CORS on Azure Front Door works automatically with no extra configuration when the **Access-Control-Allow-Origin** header is set to wildcard (*) or a single origin.  Azure Front Door caches the first response and ensuing requests use the same header.
+CORS on Azure Front Door works automatically with no extra configuration when the **Access-Control-Allow-Origin** header is set to wildcard (*) or a single origin. Azure Front Door caches the first response and ensuing requests use the same header.
 
 If requests were sent to the Azure Front Door before CORS being set on your origin, you need to purge content on your endpoint content to reload the content with the **Access-Control-Allow-Origin** header.
 
 ## Multiple origin scenarios
-If you need to allow a specific list of origins to be allowed for CORS, things get a little more complicated. The problem occurs when the CDN caches the **Access-Control-Allow-Origin** header for the first CORS origin.  When a different CORS origin makes another request, the CDN serves the cached **Access-Control-Allow-Origin** header, which doesn't match. There are several ways to correct this problem.
+If you need to allow a specific list of origins to be allowed for CORS, things get a little more complicated. The problem occurs when the CDN caches the **Access-Control-Allow-Origin** header for the first CORS origin. When a different CORS origin makes another request, the CDN serves the cached **Access-Control-Allow-Origin** header, which doesn't match. There are several ways to correct this problem.
 
 ### Azure Front Door Rule Set
 
@@ -62,9 +62,9 @@ On Azure Front Door, you can create a rule in the Azure Front Door [Rules Set](.
 :::image type="content" source="../media/troubleshooting-cross-origin-resource-sharing/cross-origin-resource.png" alt-text="Screenshot of rules example with rule set.":::
 
 > [!TIP]
-> You can add additional actions to your rule to modify additional response headers, such as **Access-Control-Allow-Methods**.
+> You can add more actions to your rule to modify other response headers, such as **Access-Control-Allow-Methods**.
 > 
 
-## Next steps
+## Next step
 
-* Learn how to [create a Front Door](create-front-door-portal.md).
+Learn how to [create a Front Door](create-front-door-portal.md).