Merge pull request #278173 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: Taojunshen

articles/cdn/cdn-create-a-storage-account-with-cdn.md

@@ -27,7 +27,7 @@ Sign in to the [Azure portal](https://portal.azure.com) with your Azure account.
 
 ## Create a storage account
 
-A storage account gives access to Azure Storage services. The storage account represents the highest level of the namespace for accessing each of the Azure Storage service components: Azure Blob, Queue, and Table storage. For more information, see [Introduction to Microsoft Azure Storage](../storage/common/storage-introduction.md).
+A storage account gives access to Azure Storage services. The storage account represents the highest level of the namespace for accessing each of the Azure Storage service components: Azure Blob, Queue, and Table storage. Take note that Azure Files can be only accessed through SMB protocol and cannot be put directly behind an Azure CDN which only supports HTTP(80) and HTTPS(443) protocols. For more information, see [Introduction to Microsoft Azure Storage](../storage/common/storage-introduction.md).
 
 To create a storage account, you must be either the service administrator or a coadministrator for the associated subscription.
 

articles/communication-services/quickstarts/call-automation/includes/quickstart-make-an-outbound-call-using-callautomation-csharp.md

@@ -36,6 +36,7 @@ devtunnel create --allow-anonymous
 devtunnel port create -p 8080
 devtunnel host
 ```
+Alternatively, follow instructions to set up your Azure DevTunnel in [Visual Studio](/aspnet/core/test/dev-tunnels)
 
 ## Update your application configuration
 
@@ -233,7 +234,7 @@ To run the application with VS Code, open a Terminal window and run the followin
 ```bash
 dotnet run
 ```
-
+Open `http://localhost:8080/swagger/index.html` or your dev tunnel URL in browser. The tunnel URL looks like: `<YOUR DEV TUNNEL ENDPOINT>/swagger/index.html`
 # [Visual Studio](#tab/visual-studio)
 
-Press Ctrl+F5 to run without the debugger.
+Press Ctrl+F5 to run the web application without the debugger. The web browser automatically opens to a tunnel URL. The tunnel URL looks like: `<YOUR DEV TUNNEL ENDPOINT>/swagger/index.html`

articles/expressroute/how-to-configure-coexisting-gateway-portal.md

@@ -26,7 +26,8 @@ Configuring Site-to-Site VPN and ExpressRoute coexisting connections has several
 The steps to configure both scenarios are covered in this article. You can configure either gateway first. Typically, you incur no downtime when adding a new gateway or gateway connection.
 
 >[!NOTE]
->If you want to create a Site-to-Site VPN over an ExpressRoute connection, see [Site-to-site over Microsoft peering](site-to-site-vpn-over-microsoft-peering.md).
+> * If you want to create a Site-to-Site VPN over an ExpressRoute connection, see [Site-to-site over Microsoft peering](site-to-site-vpn-over-microsoft-peering.md).
+> * For ExpressRoute-VPN Gateway coexistence, if you’ve already deployed an ExpressRoute, you do not need to create a virtual network and gateway subnet as these are prerequisites in creating an ExpressRoute.
 >
 
 ## Limits and limitations

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

@@ -74,7 +74,7 @@ The following table provides a comparison between Azure Front Door and Azure CDN
 | Management via REST API, .NET, de.js, or PowerShell | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
 | 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 |  |  | ✓ |  |  |  |
+| Azure Policy integration | ✓ | ✓ | ✓ |  |  |  |
 | Azure Advisory integration | ✓ | ✓ |  | ✓ | ✓ | ✓ |
 | Managed Identities with Azure Key Vault | ✓ | ✓ |  |  |  |  |
 | **Pricing** | | | | | | |

articles/time-series-insights/migration-to-fabric.md

@@ -17,7 +17,7 @@ ms.custom: attributes
 Time Series Insights is a service that enables operational analytics and reporting on historical data. It offers data ingestion, storage, contextualization, analysis, and querying capabilities. As part of migrating to [Real-Time Intelligence](/fabric/real-time-intelligence/overview), all of these capabilities can be met and even improved by migrating to [Eventhouse](/fabric/real-time-intelligence/eventhouse), the time series database in Real-Time Intelligence.
 
 > [!NOTE]
-> [Eventhouse](/fabric/real-time-intelligence/eventhouse) the evolution of [Azure Data Explorer](/azure/data-explorer/data-explorer-overview) (ADX), a service that is trusted by many customers. Eventhouse uses the strength of ADX and offers a SaaS version in Fabric Real-Time Intelligence. We recommend Eventhouse because we think it will fit your needs better. 
+> We recommend that you migrate your Time Series Insights to [Eventhouse](/fabric/real-time-intelligence/eventhouse) in Fabric Real-Time Intelligence. Eventhouse is a SaaS offering of [Azure Data Explorer](/azure/data-explorer/data-explorer-overview), a service that is trusted by many customers. However, if you want to migrate to Azure Data Explorer (the PaaS offering), you can use the guidance in the [tsi2rti repository](https://aka.ms/tsi2rti) under **Readiness**. The repository also contains tools that can help you migrate to either Eventhouse or Azure Data Explorer. 
 
 ## Migration steps