Merge pull request #289389 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/azure-maps/add-custom-protocol-pmtiles.md

@@ -20,45 +20,28 @@ By using the `addProtocol` function, which registers a callback triggered before
 The first step is to add a reference to the protocol. The following example references the `pmtiles` library:
 
 ```html
-  <script src="https://unpkg.com/pmtiles@3.0.5/dist/pmtiles.js"></script>
+  <script src="https://unpkg.com/pmtiles@3.2.0/dist/pmtiles.js"></script>
 ```
 
 Next, initialize the MapLibre PMTiles protocol.
 
 ```js
-//Initialize the plugin.
-      const protocol = new pmtiles.Protocol();
-      atlas.addProtocol("pmtiles", (request) => {
-        return new Promise((resolve, reject) => {
-          const callback = (err, data) => {
-            if (err) {
-              reject(err);
-            } else {
-              resolve({ data });
-            }
-          };
-          protocol.tile(request, callback);
-        });
-      });
-```
-
-## Add PMTiles protocol
-
-To add the PMTiles protocol, hook the data source with the specified protocol URI scheme. The following sample uses the [Overture] building dataset to add building data over the basemap.
-
-```js
-const PMTILES_URL = "https://overturemaps-tiles-us-west-2-beta.s3.amazonaws.com/2024-07-22/buildings.pmtiles";
-protocol.add(new pmtiles.PMTiles(PMTILES_URL));
+  //Initialize the plugin.
+  const protocol = new pmtiles.Protocol();
+  atlas.addProtocol("pmtiles", protocol.tile);
 ```
 
 ## Add PMTiles as a map source
 
+The following sample uses the [Overture] building dataset to add building data over the basemap.
+
 PMTiles are added as a map source during the map event. Once added, the specified URI scheme is available to the Azure Maps Web SDK. In the following sample, the PMTiles URL is added as a `VectorTileSource`.
 
 ```js
+const PMTILES_URL = "https://overturemaps-tiles-us-west-2-beta.s3.amazonaws.com/2024-07-22/buildings.pmtiles";
 //Add the source to the map.
 map.sources.add(
-  new atlas.source.VectorTileSource("pmtiles", {
+  new atlas.source.VectorTileSource("my_source", {
     type: "vector",
     url: `pmtiles://${PMTILES_URL}`,
   })
@@ -77,7 +60,7 @@ The following sample uses the building theme's properties (for example, building
 ```js
 //Create a polygon extrusion layer.
 layer = new atlas.layer.PolygonExtrusionLayer(
-  "pmtiles",
+  "my_source",
   "building",
   {
     sourceLayer: "building",

articles/azure-resource-manager/management/move-resource-group-and-subscription.md

@@ -479,6 +479,10 @@ When you receive this error, you have two options. Either move your resources to
 
 No, you can't move a resource group to a new subscription. But, you can move all of the resources in the resource group to a resource group in another subscription. Settings such as tags, role assignments, and policies aren't automatically transferred from the original resource group to the destination resource group. You need to reapply these settings to the new resource group. For more information, see [Move resources to new resource group or subscription](./move-support-resources.md).
 
+### Unsupported scenarios
+
+The platform blocks a scenario where resources from Subscription A are migrated to Subscription B when *at the same time* resources from Subscription B are migrated to Subscription C. This is by design.
+
 ## Next steps
 
 For a list of which resources support move, see [Move operation support for resources](move-support-resources.md).