Merge pull request #224005 from MicrosoftDocs/main

Publish to live, Sunday 4 p.m. PST, 1/15

Author: 19BMG00

articles/azure-monitor/logs/logs-data-export.md

@@ -34,7 +34,7 @@ Log Analytics workspace data export continuously exports data that's sent to you
 
 ## Limitations
 
-- Custom logs created via [HTTP Data Collector API](./data-collector-api.md), or 'dataSources' API won't be supported in export. Custom log created using [data collection rule](./logs-ingestion-api-overview.md) can be exported.
+- Custom logs created via [HTTP Data Collector API](./data-collector-api.md), or 'dataSources' API won't be supported in export. This includes text logs consumed by MMA. Custom log created using [data collection rule](./logs-ingestion-api-overview.md) can be exported, including text based logs.
 - We are support more tables in data export gradually, but currently limited to those specified in the [supported tables](#supported-tables) section.
 - You can define up to 10 enabled rules in your workspace, each can include multiple tables. You can create more rules in workspace in disabled state. 
 - Destinations must be in the same region as the Log Analytics workspace.

articles/azure-monitor/toc.yml

@@ -9,6 +9,8 @@ items:
     href: observability-data.md
   - name: What can you monitor?
     href: monitor-reference.md
+  - name: Optimize costs
+    href: best-practices-cost.md
   - name: What's new?
     href: whats-new.md
 - name: Concepts
@@ -1684,8 +1686,6 @@ items:
     items:
     - name: View and estimate charges
       href: usage-estimated-costs.md
-    - name: Optimize costs
-      href: best-practices-cost.md
     - name: Legacy Application Insights pricing
       href: app/legacy-pricing.md
     - name: Azure Monitor Pricing page

articles/azure-netapp-files/azacsnap-troubleshoot.md

@@ -12,7 +12,7 @@ ms.service: azure-netapp-files
 ms.workload: storage
 ms.tgt_pltfrm: na
 ms.topic: troubleshooting
-ms.date: 08/05/2022
+ms.date: 01/16/2023
 ms.author: phjensen
 ms.custom: kr2b-contr-experiment
 ---
@@ -37,7 +37,7 @@ This naming convention allows for multiple configuration files, one per database
 
 ### Result files and syslog
 
-For the `-c backup` command, AzAcSnap writes to a *\*.result* file and to the system log, `/var/log/messages`, by using the `logger` command. The *\*.result* filename has the same base name as the log file, and goes into the same location. The *\*.result* file is a simple one line output file, such as the following example:
+For the `-c backup` command, AzAcSnap writes to a *\*.result* file.  The purpose of the *\*.result* file is to provide high-level confirmation of success/failure.  If the *\*.result* file is empty, then assume failure.  Any output written to the *\*.result* file is also output to the system log (for example, `/var/log/messages`) by using the `logger` command. The *\*.result* filename has the same base name as the log file to allow for matching the result file with the configuration file and the backup log file.  The *\*.result* file goes into the same location as the other log files and is a simple one line output file, such as the following example:
 
 ```output
 Database # 1 (PR1) : completed ok

articles/frontdoor/TOC.yml

@@ -275,6 +275,8 @@
           href: front-door-how-to-onboard-apex-domain.md?pivots=front-door-standard-premium
         - name: Configure HTTPS on a custom domain
           href: standard-premium/how-to-configure-https-custom-domain.md
+        - name: Configure caching
+          href: how-to-configure-caching.md
         - name: Rules Engine
           href: standard-premium/how-to-configure-rule-set.md
         - name: Purge cache

articles/frontdoor/front-door-caching.md

@@ -7,15 +7,15 @@ ms.service: frontdoor
 ms.topic: article
 ms.tgt_pltfrm: na
 ms.workload: infrastructure-services
-ms.date: 10/31/2022
+ms.date: 01/16/2023
 ms.author: duau
 ---
 
 # Protocol support for HTTP headers in Azure Front Door
 
 This article outlines the protocol that Front Door supports with parts of the call path (see image). In the following sections, you'll find information about HTTP headers supported by Front Door.
 
-:::image type="content" source="./media/front-door-http-headers-protocol/front-door-protocol-summary.png" alt-text="Azure Front Door HTTP headers protocol":::
+:::image type="content" source="./media/front-door-http-headers-protocol/front-door-protocol-summary.png" alt-text="Diagram showing client making request to Front Door, which is forwarded to the backend. The response is sent from Front Door to the client." border="false":::
 
 > [!IMPORTANT]
 > Front Door doesn't certify any HTTP headers that aren't documented here.
@@ -45,12 +45,12 @@ Azure Front Door includes headers for an incoming request unless they're removed
 
 ## From the Front Door to the client
 
-Any headers sent to Azure Front Door from the backend are also passed through to the client. The following are headers sent from the Front Door to clients.
+Any headers sent to Azure Front Door from the backend are also passed through to the client. Front Door also attaches the following headers to all responses to the client:
 
 | Header  | Example and description |
 | ------------- | ------------- |
 | X-Azure-Ref |  *X-Azure-Ref: 0zxV+XAAAAABKMMOjBv2NT4TY6SQVjC0zV1NURURHRTA2MTkANDM3YzgyY2QtMzYwYS00YTU0LTk0YzMtNWZmNzA3NjQ3Nzgz* </br> This is a unique reference string that identifies a request served by Front Door, which is critical for troubleshooting as it's used to search access logs.|
-| X-Cache | *X-Cache:* This header describes the caching status of the request <br/> - *X-Cache: TCP_HIT*: The first byte of the request is a cache hit in the Front Door edge. <br/> - *X-Cache: TCP_REMOTE_HIT*: The first byte of the request is a cache hit in the regional cache (origin shield layer) but a miss in the edge cache. <br/> - *X-Cache: TCP_MISS*: The first byte of the request is a cache miss, and the content is served from the origin. <br/> - *X-Cache: PRIVATE_NOSTORE*: Request can't be cached as Cache-Control response header is set to either private or no-store. <br/> - *X-Cache: CONFIG_NOCACHE*: Request is configured to not cache in the Front Door profile. |
+| X-Cache | *X-Cache:* This header describes the caching status of the request. For more information, see [Caching with Azure Front Door](front-door-caching.md#response-headers). |
 
 ### Optional debug response headers
 

articles/frontdoor/front-door-http-headers-protocol.md

@@ -0,0 +1,45 @@
+---
+title: 'Configure caching - Azure Front Door'
+description: This article shows you how to configure caching on Azure Front Door.
+services: frontdoor
+author: johndowns
+ms.service: frontdoor
+ms.topic: how-to
+ms.date: 01/16/2023
+ms.author: jodowns
+---
+
+# Configure caching on Azure Front Door
+
+This article shows you how to configure caching on Azure Front Door. To learn more about caching, see [Caching with Azure Front Door](front-door-caching.md).
+
+## Prerequisites
+
+Before you can create an Azure Front Door endpoint with Front Door manager, you must have an Azure Front Door profile created. The profile must have at least one or more endpoints. To organize your Azure Front Door endpoints by internet domains, web applications, or other criteria, you can use multiple profiles. 
+
+To create an Azure Front Door profile and endpoint, see [Create an Azure Front Door profile](create-front-door-portal.md).
+
+## Configure caching by using the Azure portal
+
+1. Sign in to the [Azure portal](https://portal.azure.com?azure-portal=true) and navigate to your Azure Front Door profile.
+
+1. Select **Front Door manager** and then select your route.
+   
+    :::image type="content" source="./media/how-to-configure-caching/select-route.png" alt-text="Screenshot of endpoint landing page.":::
+
+1. Select **Enable caching**.
+
+1. Specify the query string caching behavior. For more information, see [Caching with Azure Front Door](front-door-caching.md#query-string-behavior).
+
+1. Optionally, select **Enable compression** for Front Door to compress responses to the client.
+
+1. Select **Update**.
+
+    :::image type="content" source="./media/how-to-configure-caching/update-route.png" alt-text="Screenshot of route with caching configured.":::
+
+## Next steps
+
+* Learn about the use of [origins and origin groups](origin.md) in an Azure Front Door configuration.
+* Learn about [rules match conditions](rules-match-conditions.md) in an Azure Front Door rule set.
+* Learn more about [policy settings](../web-application-firewall/afds/waf-front-door-policy-settings.md) for WAF with Azure Front Door.
+* Learn how to create [custom rules](../web-application-firewall/afds/waf-front-door-custom-rules.md) to protect your Azure Front Door profile.

articles/frontdoor/how-to-configure-caching.md

@@ -5,7 +5,7 @@ services: front-door
 author: duongau
 ms.service: frontdoor
 ms.topic: article
-ms.date: 03/20/2022
+ms.date: 01/16/2023
 ms.author: yuajia
 ---
 
@@ -19,7 +19,7 @@ There are two ways to enable file compression:
 - Enabling compression directly on the Azure Front Door POP servers (*compression on the fly*). In this case, Azure Front Door compresses the files and sends them to the end users.
 
 > [!NOTE]
-> Range requests may be compressed into different sizes. Azure Front Door requires the content-length values to be the same for any GET HTTP request. If clients send byte range requests with the `accept-encoding` header that leads to the Origin responding with different content lengths, then Azure Front Door will return a 503 error. You can either disable compression on Origin/Azure Front Door or create a Rules Set rule to remove `accept-encoding` from the request for byte range requests.
+> Range requests may be compressed into different sizes. Azure Front Door requires the `Content-Length` response header values to be the same for any GET HTTP request. If clients send byte range requests with the `Accept-Encoding` header that leads to the origin responding with different content lengths, then Azure Front Door returns a 503 error. You can either disable compression on the origin/Azure Front Door, or create a Rules Engine rule to remove the `Accept-Encoding` header from byte range requests.
 
 > [!IMPORTANT]
 > Azure Front Door configuration changes takes up to 10 mins to propagate throughout the network. If you're setting up compression for the first time for your CDN endpoint, consider waiting 1-2 hours before you troubleshoot to ensure the compression settings have propagated to all the POPs.
@@ -32,34 +32,34 @@ There are two ways to enable file compression:
 You can enable compression in the following ways:
 * During quick create - When you enable caching, you can enable compression.
 * During custom create - Enable caching and compression when you're adding a route. 
-* In Endpoint Manager route.
+* In Front Door manager.
 * On the Optimization page.
 
-### Enable compression in Endpoint manager
+### Enable compression in Front Door manager
 
-1. From the Azure Front Door Standard/Premium profile page, go to **Endpoint Manager** and select the endpoint you want to enable compression.
+1. From the Azure Front Door Standard/Premium profile page, go to **Front Door manager** and select the endpoint you want to enable compression.
 
-1. Select **Edit Endpoint**, then select the **route** you want to enable compression. 
+1. Within the endpoint, select the **route** you want to enable compression on.
 
-   :::image type="content" source="../media/how-to-compression/front-door-compression-endpoint-manager-1.png" alt-text="Screenshot of Endpoint Manager landing page." lightbox="../media/how-to-compression/front-door-compression-endpoint-manager-1-expanded.png":::   
+   :::image type="content" source="../media/how-to-compression/front-door-compression-endpoint-manager-1.png" alt-text="Screenshot of the Front Door manager landing page." lightbox="../media/how-to-compression/front-door-compression-endpoint-manager-1-expanded.png":::   
 
-1. Ensure **Enable Caching** is checked, then select the checkbox for **Enable compression**.
+1. Ensure **Enable caching** is checked, then select the checkbox for **Enable compression**.
 
-   :::image type="content" source="../media/how-to-compression/front-door-compression-endpoint-manager-2.png" alt-text="Enable compression in endpoint manager.":::   
+   :::image type="content" source="../media/how-to-compression/front-door-compression-endpoint-manager-2.png" alt-text="Screenshot of Front Door Manager showing the 'Enable compression' radio button.":::   
 
 1. Select **Update** to save the configuration.
 
-### Enable compression in Optimization
+### Enable compression in Optimizations
 
 1. From the Azure Front Door Standard/Premium profile page, go to **Optimizations** under Settings. Expand the endpoint to see the list of routes. 
 
 1. Select the three dots next to the **route** that has compression *Disabled*. Then select **Configure route**.
 
-   :::image type="content" source="../media/how-to-compression/front-door-compression-optimization-1.png" alt-text="Screen of enable compression on the optimization page." lightbox="../media/how-to-compression/front-door-compression-optimization-1-expanded.png"::: 
+   :::image type="content" source="../media/how-to-compression/front-door-compression-optimization-1.png" alt-text="Screenshot of the Optimizations page." lightbox="../media/how-to-compression/front-door-compression-optimization-1-expanded.png"::: 
 
-1. Ensure **Enable Caching** is checked, then select the checkbox for **Enable compression**.
+1. Ensure **Enable caching** is checked, then select the checkbox for **Enable compression**.
 
-     :::image type="content" source="../media/how-to-compression/front-door-compression-endpoint-manager-2.png" alt-text="Screen shot of enabling compression in endpoint manager."::: 
+     :::image type="content" source="../media/how-to-compression/front-door-compression-endpoint-manager-2.png" alt-text="Screenshot of the Optimizations page showing the 'Enable compression' radio button."::: 
 
 1. Click **Update**.
 
@@ -77,19 +77,19 @@ You can modify the default list of MIME types on Optimizations page.
 
    :::image type="content" source="../media/how-to-compression/front-door-compression-edit-content-type-2.png" alt-text="Screenshot of customize file compression page."::: 
 
-1. Select **Save**, to update compression configure .
+1. Select **Save** to update the compression configuration.
 
 ## Disabling compression
 
 You can disable compression in the following ways:
-* Disable compression in Endpoint manager route.
-* Disable compression in Optimization page.
+* Disable compression in Front Door manager route.
+* Disable compression in Optimizations page.
 
-### Disable compression in Endpoint manager
+### Disable compression in Front Door manager
 
-1. From the Azure Front Door Standard/Premium profile page, go to **Endpoint manager** under Settings. Select the endpoint you want to disable compression.
+1. From the Azure Front Door Standard/Premium profile page, go to **Front Door manager** under Settings.
 
-1. Select **Edit Endpoint** and then select the **route** you want to disable compression. Uncheck the **Enable compression** box.
+1. Select the **route** you want to disable compression on. Uncheck the **Enable compression** box.
 
 1. Select **Update** to save the configuration.