Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into esanACS

Author: roygara

.openpublishing.redirection.json

@@ -1,5 +1,45 @@
 {
     "redirections": [
+    {
+      "source_path": "articles/internet-analyzer/internet-analyzer-cli.md",
+      "redirect_url": "/previous-versions/azure/internet-analyzer/internet-analyzer-cli",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/internet-analyzer/internet-analyzer-create-test-portal.md",
+      "redirect_url": "/previous-versions/azure/internet-analyzer/internet-analyzer-create-test-portal",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/internet-analyzer/internet-analyzer-custom-endpoint.md",
+      "redirect_url": "/previous-versions/azure/internet-analyzer/internet-analyzer-custom-endpoint",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/internet-analyzer/internet-analyzer-embed-client.md",
+      "redirect_url": "/previous-versions/azure/internet-analyzer/internet-analyzer-embed-client",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/internet-analyzer/internet-analyzer-faq.md",
+      "redirect_url": "/previous-versions/azure/internet-analyzer/internet-analyzer-faq",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/internet-analyzer/internet-analyzer-overview.md",
+      "redirect_url": "/previous-versions/azure/internet-analyzer/internet-analyzer-overview",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/internet-analyzer/internet-analyzer-scorecard.md",
+      "redirect_url": "/previous-versions/azure/internet-analyzer/internet-analyzer-scorecard",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/internet-analyzer/troubleshoot.md",
+      "redirect_url": "/previous-versions/azure/internet-analyzer/troubleshoot",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/batch/batch-pool-no-public-ip-address.md",
       "redirect_url": "/previous-versions/azure/batch/articles/batch/batch-pool-no-public-ip-address",

articles/azure-arc/servers/run-command.md

@@ -2,7 +2,7 @@
 title: How to remotely and securely configure servers using Run command (Preview)
 description: Learn how to remotely and securely configure servers using Run Command.
 ms.date: 02/07/2024
-ms.topic: conceptual
+ms.topic: how-to
 ms.custom: devx-track-azurecli, devx-track-azurepowershell
 ---
 

articles/azure-monitor/alerts/action-groups.md

@@ -126,13 +126,13 @@ Alerts triggered by these alert rules contain a payload that uses the [common al
 
     Select values for these fields under **Number of violations to trigger the alert**:
 
-    |Field  |Description  |
-    |---------|---------|
-    |Number of violations|The number of violations that trigger the alert.|
-    |Evaluation period|The time period within which the number of violations occur. |
-    |Override query time range| If you want the alert evaluation period to be different than the query time range, enter a time range here.<br> The alert time range is limited to a maximum of two days. Even if the query contains an **ago** command with a time range of longer than two days, the two-day maximum time range is applied. For example, even if the query text contains **ago(7d)**, the query only scans up to two days of data. If the query requires more data than the alert evaluation you can change the time range manually. If the query contains **ago** command, it will be changed automatically to 2 days (48 hours).|
-
-    > [!NOTE]
+   |Field  |Description  |
+   |---------|---------|
+   |Number of violations|The number of violations that trigger the alert.|
+   |Evaluation period|The time period within which the number of violations occur. |
+   |Override query time range| If you want the alert evaluation period to be different than the query time range, enter a time range here.<br> The alert time range is limited to a maximum of two days. Even if the query contains an **ago** command with a time range of longer than two days, the two-day maximum time range is applied. For example, even if the query text contains **ago(7d)**, the query only scans up to two days of data. If the query requires more data than the alert evaluation, you can change the time range manually. If the query contains an **ago** command, it will be changed automatically to 2 days (48 hours).|
+   
+   > [!NOTE]
     > If you or your administrator assigned the Azure Policy **Azure Log Search Alerts over Log Analytics workspaces should use customer-managed keys**, you must select **Check workspace linked storage**. If you don't, the rule creation will fail because it won't meet the policy requirements.
 
 1. The **Preview** chart shows query evaluations results over time. You can change the chart period or select different time series that resulted from a unique alert splitting by dimensions.

articles/azure-monitor/alerts/alerts-create-log-alert-rule.md

@@ -17,7 +17,7 @@ Azure Resource Graph queries provide more functionality than the alertsSummary A
 * The ability to add new fields to the query that returns the alert summary.  
 * More flexibility in the query that returns the alert summary. 
 
-## Implementation of the current alertsSummary API: 
+## Current implementation of the alertsSummary API
 
 This is the format for the calling the alertsSummary API:
 

articles/azure-monitor/alerts/migrate-from-alerts-summary-api.md

@@ -12,7 +12,7 @@ ms.date: 03/18/2024
 ---
 
 # Azure Cosmos DB for MongoDB (vCore) with Terraform
-This document provides instructions on using Terraform to deploy Azure Cosmos DB for MongoDB vCore resources. This involves directly calling the ARM API through Terraform.
+This document provides instructions on using Terraform to deploy Azure Cosmos DB for MongoDB vCore resources. This involves directly calling the ARM API through Terraform. Full support for Terraform is targetted for the second half of 2024.
 
 ## Prerequisites
 - Terraform installed on your machine.

articles/cosmos-db/mongodb/vcore/quickstart-terraform.md

@@ -30,10 +30,11 @@ The following table provides a comparison between Azure Front Door and Azure CDN
 | Dynamic site delivery | Yes | Yes | Yes | No | Yes | Yes |
 | **Domains and Certs** | | | | | | |
 | Custom domains | Yes - DNS TXT record based domain validation | Yes - DNS TXT record based domain validation | Yes - CNAME based validation | Yes - CNAME based validation | Yes - CNAME based validation | Yes - CNAME based validation |
+| Prevalidated domain integration with Azure PaaS Service | Yes | Yes | No | No | No | No |
 | HTTPS support | Yes | Yes | Yes | Yes | Yes | Yes |
 | Custom domain HTTPS | Yes | Yes | Yes | Yes | Yes | Yes |
 | Bring your own certificate | Yes | Yes | Yes | Yes | Yes | Yes |
-| Supported TLS Versions | TLS1.2, TLS1.0 | TLS1.2, TLS1.0 | TLS1.2, TLS1.0 | TLS 1.2, TLS 1.0/1.1 | TLS 1.2, TLS 1.3 | TLS 1.2, TLS 1.3 |
+| Supported TLS Versions | TLS1.3, TLS1.2, TLS1.0 | TLS1.3 TLS1.2, TLS1.0 | TLS1.3, TLS1.2, TLS1.0 | TLS1.3, TLS 1.2, TLS 1.0/1.1 | TLS 1.2, TLS 1.3 | TLS 1.2, TLS 1.3 |
 | **Caching** | | | | | | |
 | Query string caching | Yes | Yes | Yes | Yes | Yes | Yes |
 | Cache manage (purge, rules, and compression) | Yes | Yes | Yes | Yes | Yes | Yes |
@@ -61,6 +62,8 @@ The following table provides a comparison between Azure Front Door and Azure CDN
 | Geo-filtering | Yes | Yes | Yes | Yes | Yes | Yes |
 | Token authentication | No | No | No | No | No | Yes |
 | DDOS protection | Yes | Yes | Yes | Yes | Yes | Yes |
+| DDOS protection | Yes | Yes | Yes | Yes | Yes | Yes |
+| Domain Fronting Block | Yes | Yes | Yes | Yes | Yes | Yes |
 | **Analytics and reporting** | | | | | | |
 | Monitoring Metrics | Yes (more metrics than Classic) | Yes (more metrics than Classic) | Yes | Yes | Yes | Yes |
 | Advanced analytics/built-in reports | Yes | Yes - includes WAF report | No | No | No | Yes |
@@ -72,7 +75,7 @@ The following table provides a comparison between Azure Front Door and Azure CDN
 | Compression MIME types | Configurable | Configurable | Configurable | Configurable | Configurable | Configurable |
 | Compression encodings | gzip, brotli | gzip, brotli | gzip, brotli | gzip, brotli | gzip, deflate, bzip2 | gzip, deflate, bzip2, brotli |
 | Azure Policy integration | No | No | Yes | No | No | No |
-| Azure Advisory integration | Yes | Yes | No | No | Yes | Yes |
+| Azure Advisory integration | Yes | Yes | No | Yes | Yes | Yes |
 | Managed Identities with Azure Key Vault | Yes | Yes | No | No | No | No |
 | **Pricing** | | | | | | |
 | Simplified pricing | Yes | Yes | No | Yes | Yes | Yes |

articles/frontdoor/front-door-cdn-comparison.md

@@ -1,29 +1,10 @@
 - name: Internet Analyzer Documentation
   href: index.yml
 - name: Overview
-  items: 
-  - name: About Internet Analyzer
-    href: internet-analyzer-overview.md
 - name: Tutorial
-  items:
-  - name: Create an Internet Analyzer test using Portal
-    href: internet-analyzer-create-test-portal.md
-  - name: Create an Internet Analyzer test using CLI
-    href: internet-analyzer-cli.md  
 - name: How-to guides
-  items:
-  - name: Embed client
-    href: internet-analyzer-embed-client.md
-  - name: Configure a custom endpoint
-    href: internet-analyzer-custom-endpoint.md
-  - name: Interpreting your scorecard
-    href: internet-analyzer-scorecard.md
 - name: Resources
   items:
-  - name: Internet Analyzer FAQ
-    href: internet-analyzer-faq.md
-  - name: Internet Analyzer troubleshooting
-    href: troubleshoot.md
   - name: Internet Analyzer CLI reference
     href: /cli/azure/internet-analyzer
   - name: Azure Roadmap
@@ -35,4 +16,4 @@
   - name: Preview SLA
     href: https://azure.microsoft.com/support/legal/preview-supplemental-terms
   - name: SLA
-    href: https://azure.microsoft.com/support/legal/sla
+    href: https://azure.microsoft.com/support/legal/sla