Merging changes synced from https://github.com/MicrosoftDocs/azure-docs-pr (branch live)

Author: Learn Build Service GitHub App

articles/api-center/TOC.yml

@@ -90,5 +90,7 @@
   items:
       - name: Samples and labs
         href: resources.md
+      - name: Building an API security strategy
+        href: https://aka.ms/API-Security-EBook
       - name: Azure updates
         href: https://aka.ms/apic/updates

articles/api-management/TOC.yml

@@ -657,6 +657,8 @@
       href: /azure/architecture/best-practices/api-design?toc=%2Fazure%2Fapi-management%2Ftoc.json&bc=/azure/api-management/breadcrumb/toc.json
     - name: Web API implementation
       href: /azure/architecture/best-practices/api-implementation?toc=%2Fazure%2Fapi-management%2Ftoc.json&bc=/azure/api-management/breadcrumb/toc.json
+  - name: Building an API security strategy
+    href: https://aka.ms/API-Security-EBook    
   - name: Breaking changes and retirements
     items:
     - name: Breaking changes overview

articles/api-management/authentication-authorization-overview.md

@@ -154,3 +154,4 @@ While authorization is preferred, and OAuth 2.0 has become the dominant method o
 ## Next steps
 * Learn more about [authentication and authorization](../active-directory/develop/authentication-vs-authorization.md) in the Microsoft identity platform.
 * Learn how to [mitigate OWASP API security threats](mitigate-owasp-api-threats.md) using API Management.
+* Learn how to [build a comprehensive API security strategy](https://aka.ms/API-Security-EBook)   

articles/api-management/mitigate-owasp-api-threats.md

@@ -318,5 +318,6 @@ Learn more about:
 * [Authentication and authorization in API Management](authentication-authorization-overview.md)
 * [Security baseline for API Management](/security/benchmark/azure/baselines/api-management-security-baseline)
 * [Security controls by Azure policy](security-controls-policy.md)
+* [Building a comprehensive API security strategy](https://aka.ms/API-Security-EBook)
 * [Landing zone accelerator for API Management](/azure/cloud-adoption-framework/scenarios/app-platform/api-management/landing-zone-accelerator)
 * [Microsoft Defender for Cloud](/azure/defender-for-cloud/defender-for-cloud-introduction)

articles/api-management/protect-with-defender-for-apis.md

@@ -112,4 +112,5 @@ You can remove APIs from protection by Defender for APIs by using Defender for C
 
 * Learn more about [Defender for Cloud](/azure/defender-for-cloud/defender-for-cloud-introduction)
 * Learn more about [API findings, recommendations, and alerts](/azure/defender-for-cloud/defender-for-apis-posture) in Defender for APIs
+Learn how to [build a comprehensive API security strategy](https://aka.ms/API-Security-EBook)
 * Learn how to [upgrade and scale](upgrade-and-scale.md) an API Management instance

articles/azure-app-configuration/feature-management-python-reference.md

@@ -23,7 +23,7 @@ zone_pivot_groups: feature-management
 
 :::zone target="docs" pivot="preview-version"
 
-[![Feature Management](https://img.shields.io/pypi/v/FeatureManagement/2.0.0b1?color=blue)](https://pypi.org/project/FeatureManagement/2.0.0b1/)<br>
+[![Feature Management](https://img.shields.io/pypi/v/FeatureManagement/2.0.0b2?color=blue)](https://pypi.org/project/FeatureManagement/2.0.0b2/)<br>
 
 :::zone-end
 
@@ -54,7 +54,7 @@ As an example, a Microsoft Edge browser feature filter could be designed. This f
 
 ### Feature flag configuration
 
-A Python dictionary is used to define feature flags. The dictionary is composed of feature names as keys and feature flag objects as values. The feature flag object is a dictionary that contains an `EnabledFor` key. The `EnabledFor` key is a list of feature filters that are used to determine if the feature should be enabled.
+A Python dictionary is used to define feature flags. The dictionary is composed of feature names as keys and feature flag objects as values. The feature flag object is a dictionary that contains a `conditions` key, which itself contains the `client_filters` key. The `client_filters` key is a list of feature filters that are used to determine if the feature should be enabled.
 
 ### Feature flag declaration
 

articles/azure-maps/add-custom-protocol-pmtiles.md

@@ -0,0 +1,145 @@
+---
+title: Add custom protocol PMTiles in the Web SDK | Microsoft Azure Maps
+description: Learn how to add custom protocol PMTiles using the Web SDK.
+author: sinnypan
+ms.author: sipa
+ms.date: 10/13/2024
+ms.topic: how-to
+ms.service: azure-maps
+ms.subservice: web-sdk
+---
+
+# Add custom protocol PMTiles
+
+The Azure Maps Web SDK supports custom protocols such as [PMTiles]. The `pmtiles://` protocol is used to reference PMTiles archives, which are single-file formats for storing tiled data such as vector and raster maps. This protocol allows Azure Maps to access specific tiles within a PMTiles archive using an HTTP request, fetching only the necessary data on demand.
+
+## Add custom protocol
+
+By using the `addProtocol` function, which registers a callback triggered before any AJAX request made by the library, you can intercept, modify, and return the request for further processing and rendering. This enables the implementation of a custom callback function to load resources when a URL starts with the designated custom schema.
+
+The first step is to add a reference to the protocol. The following example references the `pmtiles` library:
+
+```html
+  <script src="https://unpkg.com/[email protected]/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 URL schema. 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));
+```
+
+## Add PMTiles as a map source
+
+PMTiles are added as a map source during the map event. Once added, the specified URL schema is available to the Azure Maps Web SDK. In the following sample, the PMTiles URL is added as a `VectorTileSource`.
+
+```js
+//Add the source to the map.
+map.sources.add(
+  new atlas.source.VectorTileSource("pmtiles", {
+    type: "vector",
+    url: `pmtiles://${PMTILES_URL}`,
+  })
+);
+```
+
+> [!NOTE]
+> Using the `pmtiles://` protocol automatically creates the `minzoom` and `maxzoom` properties for the source.
+
+## Enhance map with Overture data
+
+Overture provides a unified and comprehensive [data schema] designed to organize and structure geospatial data effectively. This schema is divided into different themes, each representing a specific type of geospatial information.
+
+The following sample uses the building theme's properties (for example, building type and height) to demonstrate building extrusion and differentiate between building categories on the basemap, rather than just showing building footprints.
+
+```js
+//Create a polygon extrusion layer.
+layer = new atlas.layer.PolygonExtrusionLayer(
+  "pmtiles",
+  "building",
+  {
+    sourceLayer: "building",
+    height: ["get", "height"],
+    fillOpacity: 0.5,
+    fillColor: [
+      "case",
+      ['==', ['get', 'subtype'], 'agricultural'],
+      "wheat",
+      ['==', ['get', 'subtype'], 'civic'],
+      "teal",
+      ['==', ['get', 'subtype'], 'commercial'],
+      "blue",
+      ['==', ['get', 'subtype'], 'education'],
+      "aqua",
+      ['==', ['get', 'subtype'], 'entertainment'],
+      "pink",
+      ['==', ['get', 'subtype'], 'industrial'],
+      "yellow",
+      ['==', ['get', 'subtype'], 'medical'],
+      "red",
+      ['==', ['get', 'subtype'], 'military'],
+      "darkgreen",
+      ['==', ['get', 'subtype'], 'outbuilding'],
+      "white",
+      ['==', ['get', 'subtype'], 'religious'],
+      "khaki",
+      ['==', ['get', 'subtype'], 'residential'],
+      "green",
+      ['==', ['get', 'subtype'], 'service'],
+      "gold",
+      ['==', ['get', 'subtype'], 'transportation'],
+      "orange",
+      "grey",
+    ],
+    filter: ['any', ['==', ['geometry-type'], 'Polygon'], ['==', ['geometry-type'], 'MultiPolygon']]
+  }
+);
+```
+
+The following image shows a screenshot displaying the extrusion of buildings of different types near Central Park in New York City.
+
+:::image type="content" source="media/add-custom-protocol-pmtiles/pmtiles-building.png"  lightbox="media/add-custom-protocol-pmtiles/pmtiles-building.png" alt-text="A screenshot demonstrating the custom protocol pmtiles.":::
+
+For a fully functional sample with source code, see [Azure Maps Samples GitHub Repo].
+
+<!--
+For more PMTiles samples, see [Azure Maps Samples].
+[Azure Maps Samples]: https://samples.azuremaps.com/?search=pmtiles
+-->
+
+## Next Steps
+
+The following articles are related to custom protocol PMTiles:
+
+> [!div class="nextstepaction"]
+> [Create Data Source](create-data-source-web-sdk.md)
+
+> [!div class="nextstepaction"]
+> [Data Driven Style Expressions](data-driven-style-expressions-web-sdk.md)
+
+[Azure Maps Samples GitHub Repo]: https://github.com/Azure-Samples/AzureMapsCodeSamples/blob/main/Samples/PMTiles/Overture%20Building%20Theme/Buildings.html
+[data schema]: https://docs.overturemaps.org/schema
+[Overture]: https://overturemaps.org
+[PMTiles]: https://docs.protomaps.com/pmtiles

articles/azure-maps/media/add-custom-protocol-pmtiles/pmtiles-building.png

@@ -147,6 +147,142 @@ The **polygons** section of the format visual pane:
 
 :::image type="content" source="./media/power-bi-visual/polygons.png" alt-text="A screenshot displaying the polygons section of the format visual pane.":::
 
+## Data-Bound Reference Layer
+
+The Data-Bound Reference Layer enables the association of data with specific shapes in the reference layer based on common attributes.
+
+To use the Data-Bound Reference layer, drag the column containing unique identifiers (can be location data or not) to the Location field of the Azure Maps Visual.
+
+:::image type="content" source="media/power-bi-visual/data-bound-reference-layer/location-field.png" alt-text="A screenshot showing the location field in Power BI desktop.":::
+
+Azure Maps matches these identifiers with the corresponding properties in the uploaded spatial file, automatically linking your data to the shapes on the map.
+
+In scenarios with multiple properties, Azure Maps identifies a common property in each shape and compares its value with the selected data column in the Location field. It then uses the property that has the highest number of matches with the selected data column.
+
+:::image type="content" source="media/power-bi-visual/data-bound-reference-layer/data-bound-reference-layer.png"  lightbox="media/power-bi-visual/data-bound-reference-layer/data-bound-reference-layer.png" alt-text="A screenshot showing the Data-Bound Reference Layer example in Power BI desktop.":::
+
+If one or more shapes in the reference layer can't be automatically mapped to any data point, you can manage these unmapped objects by following these steps:
+
+1. Select the **Format visual** tab in the **Visualizations** pane.
+1. Select **Reference layer**.
+1. Select **Unmapped Objects**.
+1. Select the **Show** toggle switch to toggle On/Off. This highlights shapes that aren't mapped to any data points.
+
+Optionally, select the **Use custom colors** toggle switch to toggle On/Off custom fill and border colors for unmapped objects to make them visually distinct on the map.
+
+:::image type="content" source="media/power-bi-visual/data-bound-reference-layer/data-bound-reference-layer-unmapped-objects.png" lightbox="media/power-bi-visual/data-bound-reference-layer/data-bound-reference-layer-unmapped-objects.png" alt-text="A screenshot showing the Data-Bound Reference Layer example in Power BI desktop with unmapped objects showing in a different color.":::
+
+<!----------------------------------------------------------------------------
+### Key matching example
+
+#### Semantic model
+
+| Datapoint   | Country | City     | Office name |
+|-------------|---------|----------|-------------|
+| Datapoint_1 | US      | New York | Office C    |
+| Datapoint_1 | US      | Seattle  | Office A    |
+| Datapoint_1 | US      | LA       | Office B    |
+
+#### Reference layer data (take GeoJSON as an example)
+
+```json
+{
+  "type": "FeatureCollection",
+  "features": [
+    {
+      "type": "Feature",
+      "properties": {
+        "name": "Office A",
+        "shape": "Shape_1",
+        "id": "Office A"
+      },
+      "geometry": {
+        "type": "Polygon",
+        "coordinates": [
+          ...
+      }
+    },
+    {
+      "type": "Feature",
+      "properties": {
+        "name": "Office B",
+        "shape": "Shape_2",
+        "id": "Office B"
+      },
+      "geometry": {
+        "type": "Point",
+        "coordinates": [
+          ...
+        ]
+      }
+    },
+    {
+      "type": "Feature",
+      "properties": {
+        "name": "Office C",
+        "shape": "Shape_3"
+      },
+      "geometry": {
+        "type": "Point",
+        "coordinates": [
+          ...
+        ]
+      }
+    },
+    {
+      "type": "Feature",
+      "properties": {
+        "name": "Office D",
+        "shape": "Shape_4"
+      },
+      "geometry": {
+        "type": "Polygon",
+        "coordinates": [
+          ...
+        ]
+      }
+    }
+  ]
+}
+```
+
+#### the mapping results
+
+|                 | Location bucket|Mapping result                                                                  |
+|-----------------|----------------|--------------------------------------------------------------------------------|
+| Case 1          | Office name    | Shape_1 ↔ Datapoint_2                                                          |
+|                 |                | Shape_2 ↔ Datapoint_3                                                          |
+|                 |                | Shape_3 ↔ Datapoint_1                                                          |
+|                 |                | Shape_4 ↔ x (Since there’s no datapoint with Office name “Office D”)           |
+| Case 2          | City           | Nothing is mapped, since there’s no property that contains matched City names. |
+
+Note that there is a property “id” also has “Office x” values that is not being used, but instead the property “name” is used for data mapping since it has 3 datapoints matched and “id” only has 2 datapoints matched.
+
+---------------------------------------------------------------------------------------------------------------------------->
+
+## Conditional Formatting
+
+Conditional formatting can be applied to data to dynamically change the appearance of shapes on a map based on the provided data. For instance, gradient colors can visualize various data values such as population density, sales performance, or other metrics. This is a powerful tool for combining spatial and business data to create interactive and visually compelling reports.
+
+:::image type="content" source="media/power-bi-visual/data-bound-reference-layer/conditional-formatting.png" alt-text="A screenshot showing the Conditional Formatting controls for points, lines, polygons, and unmanaged objects in the reference layer control in Power BI desktop.":::
+
+There are several ways to set colors to the shapes. The following table shows the priorities used:
+
+| Priority | Source                        | Description                                                     |
+|----------|-------------------------------|-----------------------------------------------------------------|
+| 1        | Preset style in spatial files | Color and style as defined in the spatial file                  |
+| 2        | Unmapped object colors        | Custom colors used when the geometry isn’t data-bound           |
+| 3        | Legend colors                 | Colors provided by Legend/Series                                |
+| 4        | Conditional formatting colors | Colors provided by conditional formatting                       |
+| 5        | Custom formatting colors      | User defined custom styles in the Reference Layer options in the formatting pane |
+| 6        | Default colors                | Default colors defined in the Azure Maps visual                 |
+
+> [!TIP]
+>
+> The Azure Maps Power BI Visual can only perform geocoding on valid location data such as geographical coordinates, addresses, or place names. If no valid location data is uploaded, data layers that depend on geocoded locations, such as heat maps or bubble layers, won’t display on the map.
+>
+> The Data-Bound Reference Layer will appear on the map as long as the data column contains unique identifiers that match properties in the spatial file, but to ensure correct results, your data column must include valid geographic information.
+
 ## Next steps
 
 Add more context to the map: