Merge pull request #242649 from MicrosoftDocs/repo_sync_working_branch

huypub · web-flow · commit 793fe2a9c843 · 2023-06-23T09:54:14.000-07:00
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
diff --git a/articles/app-service/language-support-policy.md b/articles/app-service/language-support-policy.md
@@ -1,8 +1,7 @@
 ---
 title: Language Support Policy
 description: App Service language runtime support policies 
-author: jeffmartinez
-
+author: jeffwmartinez
 ms.topic: article
 ms.date: 01/23/2023
 ms.author: jefmarti
@@ -31,8 +30,8 @@ Those who receive notifications include account administrators, service administ
 ## Language runtime version support timelines
 To learn more about specific language support policy timelines, visit the following resources:
 
-- [ASP.NET](https://aka.ms/aspnetrelease)
-- [.NET](https://aka.ms/dotnetrelease)
+- [.NET and ASP.NET Core](https://aka.ms/dotnetrelease)
+- [.NET Framework and ASP.NET](https://aka.ms/aspnetrelease)
 - [Node](https://aka.ms/noderelease)
 - [Java](https://aka.ms/javarelease)
 - [Python](https://aka.ms/pythonrelease)
@@ -48,4 +47,4 @@ To learn more about how to update your App Service application language versions
 - [Node](https://github.com/Azure/app-service-linux-docs/blob/master/Runtime_Support/node_support.md#node-on-linux-app-service)
 - [Java](https://github.com/Azure/app-service-linux-docs/blob/master/Runtime_Support/java_support.md#java-on-app-service)
 - [Python](https://github.com/Azure/app-service-linux-docs/blob/master/Runtime_Support/python_support.md#how-to-update-your-app-to-target-a-different-version-of-python)
-- [PHP](https://github.com/Azure/app-service-linux-docs/blob/master/Runtime_Support/php_support.md#how-to-update-your-app-to-target-a-different-version-of-php)
+- [PHP](https://github.com/Azure/app-service-linux-docs/blob/master/Runtime_Support/php_support.md#how-to-update-your-app-to-target-a-different-version-of-php)
diff --git a/articles/azure-maps/index.yml b/articles/azure-maps/index.yml
@@ -65,7 +65,7 @@ landingContent:
             url: how-to-view-api-usage.md
 
   # Card
-  - title: Developing with Creator
+  - title: Indoor maps using Azure Maps Creator
     linkLists:
       - linkListType: concept
         links:
@@ -81,22 +81,28 @@ landingContent:
             url: how-to-manage-creator.md
           - text: Implement Dynamic styling for indoor maps
             url: indoor-map-dynamic-styling.md
-          - text: Use Azure Maps drawing error visualizer
-            url: drawing-error-visualizer.md
-          - text: Use the indoor map module
-            url: how-to-use-indoor-module.md
-          - text: Use Azure Digital Twins to update indoor map
-            url: ../digital-twins/how-to-integrate-maps.md
+          - text: Query datasets with WFS API
+            url: how-to-creator-wfs.md
+          - text: Custom styling for indoor maps
+            url: how-to-create-custom-styles.md
+          - text: Indoor maps wayfinding service
+            url: how-to-creator-wayfinding.md
+          - text: Edit indoor maps using the QGIS plugin
+            url: creator-qgis-plugin.md
+          - text: Create dataset using GeoJson package
+            url: how-to-dataset-geojson.md
+          - text: Create a feature stateset
+            url: how-to-creator-feature-stateset.md
       - linkListType: reference
         links:
-          - text: Conversion service
-            url: /rest/api/maps/v2/conversion
-          - text: Dataset service
-            url: /rest/api/maps/v2/dataset
-          - text: Tileset service
-            url: /rest/api/maps/v2/tileset
-          - text: Feature stateset service
-            url: /rest/api/maps/v2/feature-state
+            - text: Drawing package requirements
+              url: drawing-requirements.md
+            - text: Facility Ontology
+              url: creator-facility-ontology.md
+            - text: Dynamic maps StylesObject
+              url: schema-stateset-stylesobject.md
+            - text: Drawing error visualizer
+              url: drawing-error-visualizer.md
                     
   # Card
   - title: Developing with Web SDK
diff --git a/articles/azure-maps/supported-browsers.md b/articles/azure-maps/supported-browsers.md
@@ -1,10 +1,11 @@
 ---
-title: Web SDK supported browsers | Microsoft Azure Maps
+title: Web SDK supported browsers
+titleSuffix: Microsoft Azure Maps
 description: Find out how to check whether the Azure Maps Web SDK supports a browser. View a list of supported browsers. Learn how to use map services with legacy browsers.
 author: eriklindeman
 ms.author: eriklind
-ms.date: 03/25/2019
-ms.topic: conceptual
+ms.date: 06/22/2023
+ms.topic: how-to
 ms.service: azure-maps
 ms.custom: devx-track-js
 ---
@@ -57,23 +58,32 @@ The following Web SDK modules are also supported in Node.js:
 
 ## <a name="Target-Legacy-Browsers"></a>Target legacy browsers
 
-You might want to target older browsers that don't support WebGL or that have only limited support for it. In such cases, we recommend that you use Azure Maps services together with an open-source map control like [Leaflet](https://leafletjs.com/). Here's an example that makes use of the open source [Azure Maps Leaflet plugin](https://github.com/azure-samples/azure-maps-leaflet).
+You might want to target older browsers that don't support WebGL or that have only limited support for it. In such cases, you can use Azure Maps services together with an open-source map control like [Leaflet](https://leafletjs.com/).
 
-<br/>
+The [Render Azure Maps in Leaflet] Azure Maps sample shows how to render Azure Maps Raster Tiles in the Leaflet JS map control. This sample uses the open source [Azure Maps Leaflet plugin]. For the source code for this sample, see [Render Azure Maps in Leaflet sample source code].
 
+<!----------------------------------------
 <iframe height="500" scrolling="no" title="Azure Maps + Leaflet" src="//codepen.io/azuremaps/embed/GeLgyx/?height=500&theme-id=0&default-tab=html,result" frameborder="no" allowtransparency="true" allowfullscreen="true">
   See the Pen <a href='https://codepen.io/azuremaps/pen/GeLgyx/'>Azure Maps + Leaflet</a> by Azure Maps
-  (<a href='https://codepen.io/azuremaps'>@azuremaps</a>) on <a href='https://codepen.io'>CodePen</a>.
-</iframe>
+  (<a href='https://codepen.io/azuremaps'>@azuremaps</a>) on <a href='https://codepen.io'>CodePen</a>.</iframe>
+---------------------------------------->
 
-For code samples using Azure Maps in Leaflet, see [Azure Maps Samples](https://samples.azuremaps.com/?search=leaflet).
+For more code samples using Azure Maps in Leaflet, see [Azure Maps Samples].
 
-For a list of third-party map control plug-ins, see [Azure Maps community - Open-source projects](open-source-projects.md#third-part-map-control-plugins).
+For a list of third-party map control plug-ins, see [Azure Maps community - Open-source projects].
 
 ## Next steps
 
 Learn more about the Azure Maps Web SDK:
 
-[Map control](how-to-use-map-control.md)
+> [!div class="nextstepaction"]
+> [Map control](how-to-use-map-control.md)
 
-[Services module](how-to-use-services-module.md)
+> [!div class="nextstepaction"]
+> [Services module](how-to-use-services-module.md)
+
+[Render Azure Maps in Leaflet]: https://samples.azuremaps.com/third-party-map-controls/render-azure-maps-in-leaflet
+[Render Azure Maps in Leaflet sample source code]: https://github.com/Azure-Samples/AzureMapsCodeSamples/blob/main/Samples/Third%20Party%20Map%20Controls/Render%20Azure%20Maps%20in%20Leaflet/Render%20Azure%20Maps%20in%20Leaflet.html
+[Azure Maps Leaflet plugin]: https://github.com/azure-samples/azure-maps-leaflet
+[Azure Maps Samples]: https://samples.azuremaps.com/?search=leaflet
+[Azure Maps community - Open-source projects]: open-source-projects.md#third-part-map-control-plugins
diff --git a/articles/azure-maps/toc.yml b/articles/azure-maps/toc.yml
@@ -137,20 +137,20 @@ items:
     items:
     - name: Manage Creator
       href: how-to-manage-creator.md
+    - name: Drawing package guide
+      href: drawing-package-guide.md
     - name: Query datasets with WFS API
       href: how-to-creator-wfs.md
-    - name: Create a feature stateset
-      href: how-to-creator-feature-stateset.md
     - name: Custom styling for indoor maps
       href: how-to-create-custom-styles.md
     - name: Indoor maps wayfinding service
       href: how-to-creator-wayfinding.md
-    - name: Drawing package guide
-      href: drawing-package-guide.md
-    - name: Create dataset using GeoJson package
-      href: how-to-dataset-geojson.md
     - name: Edit indoor maps using the QGIS plugin
       href: creator-qgis-plugin.md
+    - name: Create dataset using GeoJson package
+      href: how-to-dataset-geojson.md
+    - name: Create a feature stateset
+      href: how-to-creator-feature-stateset.md
   - name: Get map data from REST APIs
     items:
     - name: Search for an address
@@ -388,17 +388,15 @@ items:
 - name: Reference
   items:
   - name: Creator Indoor Maps
-    items:   
-    - name: Drawing error visualizer
-      href: drawing-error-visualizer.md
+    items:
     - name: Drawing package requirements
       href: drawing-requirements.md
-    - name: Drawing conversion errors and warnings
-      href: drawing-conversion-error-codes.md
-    - name: Dynamic maps StylesObject
-      href: schema-stateset-stylesobject.md
     - name: Facility Ontology
       href: creator-facility-ontology.md
+    - name: Dynamic maps StylesObject
+      href: schema-stateset-stylesobject.md
+    - name: Drawing error visualizer
+      href: drawing-error-visualizer.md
   - name: API and parameter extensions
     items:
     - name: Vehicle consumption model
diff --git a/articles/communication-services/concepts/telephony/inbound-calling-capabilities.md b/articles/communication-services/concepts/telephony/inbound-calling-capabilities.md
@@ -20,7 +20,7 @@ Inbound PSTN calling is currently supported in GA for Dynamics Omnichannel. You
 
 Supported in General Availability, to set up inbound calling in Omnichannel for Customer Service with direct routing or Voice Calling (PSTN) follow [these instructions](/dynamics365/customer-service/voice-channel-inbound-calling).
 
-**Inbound calling with ACS Call Automation SDK**
+**Inbound calling with Azure Communication Services Call Automation SDK**
 
 Call Automation enables you to build custom calling workflows within your applications to optimize business processes and boost customer satisfaction. The library supports managing incoming calls to the phone numbers acquired from Communication Services and incoming calls via Direct Routing. You can also use Call Automation to place outbound calls from the phone numbers owned by your resource, among other capabilities.   
 
diff --git a/articles/sentinel/normalization-schema-dhcp.md b/articles/sentinel/normalization-schema-dhcp.md
@@ -95,7 +95,7 @@ The fields below are specific to DHCP events, but many are similar to fields in
 | <a name="srcmacaddr"></a>**SrcMacAddr** | Mandatory | Mac Address | The MAC address of the client requesting a DHCP lease. <br><br>**Note**: The Windows DHCP server logs MAC address in a non-standard way, omitting the colons, which should be inserted by the parser.<br><br>Example: `06:10:9f:eb:8f:14` |
 | <a name="dhcpleaseduration"></a>**DhcpLeaseDuration** | Optional | Integer | The length of the lease granted to a client, in seconds. |  
 |<a name="dhcpsessionid"></a>**DhcpSessionId** | Optional | string | The session identifier as reported by the reporting device. For the Windows DHCP server, set this to the TransactionID field. <br><br>Example: `2099570186` |
-| **SessionId** | Alias | String | Alias to [DhcpkSessionId](#dhcpsessionid) |
+| **SessionId** | Alias | String | Alias to [DhcpSessionId](#dhcpsessionid) |
 | <a name="dhcpsessionduration"></a>**DhcpSessionDuration** | Optional | Integer | The amount of time, in milliseconds, for the completion of the DHCP session.<br><br>Example: `1500` |
 | **Duration** | Alias | | Alias to [DhcpSessionDuration](#dhcpsessionduration) |
 | **DhcpSrcDHCId** | Optional | String | The DHCP client ID, as defined by [RFC4701](https://datatracker.ietf.org/doc/html/rfc4701) |
diff --git a/articles/stream-analytics/azure-database-explorer-output.md b/articles/stream-analytics/azure-database-explorer-output.md
@@ -67,7 +67,7 @@ You can significantly grow the scope of real-time analytics by using Azure Strea
 * The name of the columns and data type should match between the Azure Stream Analytics SQL query and the Azure Data Explorer table. The comparison is case-sensitive.
 * Columns that exist in your Azure Data Explorer clusters but are missing in Azure Stream Analytics are ignored. Columns that are missing in Azure Stream Analytics raise an error.
 * The order of your columns in your Azure Stream Analytics query doesn't matter. The schema of the Azure Data Explorer table determines the order.
-* Azure Data Explorer has an aggregation (batching) policy for data ingestion that's designed to optimize the ingestion process. The policy is configured to 5 minutes, 1,000 items, or 1 GB of data by default, so you might experience a latency. For aggregation options, see [IngestionBatching policy](/azure/data-explorer/kusto/management/batchingpolicy).
+* Azure Data Explorer has an aggregation (batching) policy for data ingestion that's designed to optimize the ingestion process. The policy is configured to 5 minutes, 1,000 items, or 1 GB of data by default, so you might experience a latency. To reduce latency, enable streaming ingestion on your cluster, and then table or database by following the steps in [Configure streaming ingestion on your Azure Data Explorer cluster](/azure/data-explorer/ingest-data-streaming). For aggregation options, see [IngestionBatching policy](/azure/data-explorer/kusto/management/batchingpolicy).
 
 ## Next steps
 
diff --git a/articles/virtual-network/network-security-group-how-it-works.md b/articles/virtual-network/network-security-group-how-it-works.md
@@ -48,7 +48,7 @@ For outbound traffic, Azure processes the rules in a network security group asso
 
 ## Intra-Subnet traffic
 
-It's important to note that security rules in an NSG associated to a subnet can affect connectivity between VMs within it. By default, virtual machines in the same subnet can communicate based on a default NSG rule allowing intra-subnet traffic. If you add a rule to *NSG1* that denies all inbound and outbound traffic, *VM1* and *VM2* won't able to communicate with each other.
+It's important to note that security rules in an NSG associated to a subnet can affect connectivity between VMs within it. By default, virtual machines in the same subnet can communicate based on a default NSG rule allowing intra-subnet traffic. If you add a rule to *NSG1* that denies all inbound and outbound traffic, *VM1* and *VM2* won't be able to communicate with each other.
 
 You can easily view the aggregate rules applied to a network interface by viewing the [effective security rules](virtual-network-network-interface.md#view-effective-security-rules) for a network interface. You can also use the [IP flow verify](../network-watcher/diagnose-vm-network-traffic-filtering-problem.md?toc=%2fazure%2fvirtual-network%2ftoc.json) capability in Azure Network Watcher to determine whether communication is allowed to or from a network interface. You can use IP flow verify to determine whether a communication is allowed or denied. Additionally, Use IP flow verify to surface the identity of the network security rule responsible for allowing or denying the traffic.
 
