Skip to content

Commit a69d2ab

Browse files
authored
Merge pull request #270599 from MicrosoftDocs/main
3/29 11:00 AM IST Publish
2 parents c8c9b07 + 43fa579 commit a69d2ab

File tree

37 files changed

+899
-274
lines changed

37 files changed

+899
-274
lines changed

articles/api-center/enable-api-analysis-linting.md

Lines changed: 11 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Perform API linting and analysis - Azure API Center
33
description: Configure linting of API definitions in your API center to analyze compliance of APIs with the organization's API style guide.
44
ms.service: api-center
55
ms.topic: how-to
6-
ms.date: 03/11/2024
6+
ms.date: 03/26/2024
77
ms.author: danlep
88
author: dlepow
99
ms.custom: devx-track-azurecli
@@ -85,20 +85,16 @@ Follow these steps to deploy the Azure Functions app that runs the linting funct
8585

8686
To enable the function app to access the API center, configure a managed identity for the function app. The following steps show how to enable and configure a system-assigned managed identity for the function app using the Azure portal or the Azure CLI.
8787

88-
> [!NOTE]
89-
> In preview, this scenario requires the Contributor role to be assigned to the function app's managed identity.
90-
91-
9288
#### [Portal](#tab/portal)
9389

9490
1. In the Azure portal, navigate to your function app and select **Identity** under the **Settings** section.
9591
1. On the **System assigned** tab, set the **Status** to **On** and then select **Save**.
9692

97-
Now that the managed identity is enabled, assign it the Contributor role to access the API center.
93+
Now that the managed identity is enabled, assign it the Azure API Center Compliance Manager role to access the API center.
9894

99-
1. In the Azure portal, navigate to your API center and select **Access control (IAM)**.
95+
1. In the [Azure portal](https://portal.azure.com), navigate to your API center and select **Access control (IAM)**.
10096
1. Select **+ Add > Add role assignment**.
101-
1. Select **Privileged administrator roles** and then select **Contributor**. Select **Next**.
97+
1. Select **Job function roles** and then select **Azure API Center Compliance Manager**. Select **Next**.
10298
1. On the **Members** page, in **Assign access to**, select **Managed identity > + Select members**.
10399
1. On the **Select managed identities** page, search for and select the managed identity of the function app. Click **Select** and then **Next**.
104100
1. Review the role assignment, and select **Review + assign**.
@@ -136,12 +132,12 @@ Now that the managed identity is enabled, assign it the Contributor role to acce
136132
--query "id" --output tsv)
137133
```
138134
139-
1. Assign the function app's managed identity the Contributor role in the API center using the [az role assignment create](/cli/azure/role/assignment#az-role-assignment-create) command.
135+
1. Assign the function app's managed identity the Azure API Center Compliance Manager role in the API center using the [az role assignment create](/cli/azure/role/assignment#az-role-assignment-create) command.
140136
141137
```azurecli
142138
#! /bin/bash
143139
az role assignment create \
144-
--role "Contributor" \
140+
--role "Azure API Center Compliance Manager" \
145141
--assignee-object-id $principalID \
146142
--assignee-principal-type ServicePrincipal \
147143
--scope $apicID
@@ -150,7 +146,7 @@ Now that the managed identity is enabled, assign it the Contributor role to acce
150146
```azurecli
151147
# PowerShell syntax
152148
az role assignment create `
153-
--role "Contributor" `
149+
--role "Azure API Center Compliance Manager" `
154150
--assignee-object-id $principalID `
155151
--assignee-principal-type ServicePrincipal `
156152
--scope $apicID
@@ -164,9 +160,8 @@ Now create an event subscription in your API center to trigger the function app
164160
165161
#### [Portal](#tab/portal)
166162
167-
1. Sign in to the Azure portal at [https://portal.azure.com/?Microsoft_Azure_ApiManagement=apicenterpreview](https://portal.azure.com/?Microsoft_Azure_ApiManagement=apicenterpreview). Currently for this scenario, you must access your API center in the portal at this feature flag.
168-
1. Navigate to your API center and select **Events**.
169-
1. Select **Azure Function**.
163+
1. In the [Azure portal](https://portal.azure.com), navigate to your API center and select **Events**.
164+
1. On the **Get started** tab, select **Azure Function**.
170165
1. On the **Create Event Subscription** page, do the following:
171166
1. Enter a descriptive **Name** for the event subscription, and select **Event Grid Schema**.
172167
1. In **Topic details**, enter a **System topic name** of your choice.
@@ -251,7 +246,6 @@ To test the event subscription, try uploading or updating an API definition file
251246
252247
To confirm that the event subscription was triggered:
253248
254-
1. Sign in to the Azure portal at [https://portal.azure.com/?Microsoft_Azure_ApiManagement=apicenterpreview](https://portal.azure.com/?Microsoft_Azure_ApiManagement=apicenterpreview).
255249
1. Navigate to your API center, and select **Events** in the left menu.
256250
1. Select the **Event Subscriptions** tab and select the event subscription for your function app.
257251
1. Review the metrics to confirm that the event subscription was triggered and that linting was invoked successfully.
@@ -273,8 +267,7 @@ In the portal, you can also view a summary of analysis reports for all API defin
273267
274268
To view the analysis report for an API definition in your API center:
275269
276-
1. Sign in to the Azure portal at [https://portal.azure.com/?Microsoft_Azure_ApiManagement=apicenterpreview](https://portal.azure.com/?Microsoft_Azure_ApiManagement=apicenterpreview).
277-
1. Navigate to the API version in your API center where you added or updated an API definition.
270+
1. In the portal, navigate to the API version in your API center where you added or updated an API definition.
278271
1. Select **Definitions**, and then select the API definition file that you uploaded or updated.
279272
1. Select the **Analysis** tab.
280273
:::image type="content" source="media/enable-api-analysis-linting/analyze-api-definition.png" alt-text="Screenshot of Analysis tab for API definition in the portal.":::
@@ -287,7 +280,7 @@ The **API Analysis Report** opens, and it displays the API definition and errors
287280
288281
To view a summary of analysis reports for all API definitions in your API center:
289282
290-
1. Sign in to the Azure portal at [https://portal.azure.com/?Microsoft_Azure_ApiManagement=apicenterpreview](https://portal.azure.com/?Microsoft_Azure_ApiManagement=apicenterpreview).
283+
1. In the portal, navigate to your API center.
291284
1. In the left-hand menu, under **Governance**, select **API Analysis**. The summary appears.
292285
293286
:::image type="content" source="media/enable-api-analysis-linting/api-analysis-summary.png" alt-text="Screenshot of the API analysis summary in the portal.":::

articles/azure-arc/resource-bridge/troubleshoot-resource-bridge.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -95,7 +95,7 @@ Arc resource bridge consists of an appliance VM that is deployed to the on-premi
9595

9696
### Private Link is unsupported
9797

98-
Arc resource bridge doesn'tt support private link. All calls coming from the appliance VM shouldn't be going through your private link setup. The Private Link IPs may conflict with the appliance IP pool range, which isn't configurable on the resource bridge. Arc resource bridge reaches out to [required URLs](network-requirements.md#firewallproxy-url-allowlist) that shouldn't go through a private link connection. You must deploy Arc resource bridge on a separate network segment unrelated to the private link setup.
98+
Arc resource bridge doesn't support private link. All calls coming from the appliance VM shouldn't be going through your private link setup. The Private Link IPs may conflict with the appliance IP pool range, which isn't configurable on the resource bridge. Arc resource bridge reaches out to [required URLs](network-requirements.md#firewallproxy-url-allowlist) that shouldn't go through a private link connection. You must deploy Arc resource bridge on a separate network segment unrelated to the private link setup.
9999

100100

101101
## Networking issues

articles/azure-maps/how-to-use-best-practices-for-routing.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -265,6 +265,12 @@ The following image is an example of rendering alternative routes with specified
265265

266266
The Azure Maps Web SDK provides a [Service module]. This module is a helper library that makes it easy to use the Azure Maps REST APIs in web or Node.js applications, using JavaScript or TypeScript. The Service module can be used to render the returned routes on the map. The module automatically determines which API to use with GET and POST requests.
267267

268+
> [!NOTE]
269+
>
270+
> **Azure Maps Web SDK Service Module retirement**
271+
>
272+
> The Azure Maps Web SDK Service Module is now deprecated and will be retired on 9/30/26. To avoid service disruptions, we recommend migrating to the Azure Maps JavaScript REST SDK by 9/30/26. For more information, see [JavaScript/TypeScript REST SDK Developers Guide (preview)](how-to-dev-guide-js-sdk.md).
273+
268274
## Next steps
269275

270276
To learn more, please see:

articles/azure-maps/how-to-use-services-module.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ titleSuffix: Microsoft Azure Maps
44
description: Learn about the Azure Maps services module. See how to load and use this helper library to access Azure Maps REST services in web or Node.js applications.
55
author: sinnypan
66
ms.author: sipa
7-
ms.date: 06/26/2023
7+
ms.date: 03/27/2024
88
ms.topic: how-to
99
ms.service: azure-maps
1010
services: azure-maps
@@ -15,6 +15,12 @@ ms.custom: devx-track-js
1515

1616
The Azure Maps Web SDK provides a [services module]. This module is a helper library that makes it easy to use the Azure Maps REST services in web or Node.js applications by using JavaScript or TypeScript.
1717

18+
> [!NOTE]
19+
>
20+
> **Azure Maps Web SDK Service Module retirement**
21+
>
22+
> The Azure Maps Web SDK Service Module is now deprecated and will be retired on 9/30/26. To avoid service disruptions, we recommend migrating to the Azure Maps JavaScript REST SDK by 9/30/26. For more information, see [JavaScript/TypeScript REST SDK Developers Guide (preview)](how-to-dev-guide-js-sdk.md).
23+
1824
## Use the services module in a webpage
1925

2026
1. Create a new HTML file.

articles/azure-maps/release-notes-map-control.md

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,11 +16,19 @@ This document contains information about new features and other changes to the M
1616

1717
## v3 (latest)
1818

19+
### [3.2.0] (March 29, 2024)
20+
21+
#### Other changes (3.2.0)
22+
23+
- Upgrade MapLibre to [V4](https://github.com/maplibre/maplibre-gl-js/releases/tag/v4.0.0).
24+
25+
- Correct the default value of `HtmlMarkerOptions.pixelOffset` from `[0, -18]` to `[0, 0]` in the doc.
26+
1927
### [3.1.2] (February 22, 2024)
2028

2129
#### New features (3.1.2)
2230

23-
- Added `fillAntialias` option to `PolygonLayer` for enabling MSAA on polygon fills.
31+
- Added `fillAntialias` option to `PolygonLayer` for enabling MSAA antialiasing on polygon fills.
2432

2533
#### Other changes (3.1.2)
2634

@@ -411,7 +419,7 @@ This update is the first preview of the upcoming 3.0.0 release. The underlying [
411419

412420
#### New features (2.3.7)
413421

414-
- Added `fillAntialias` option to `PolygonLayer` for enabling MSAA on polygon fills.
422+
- Added `fillAntialias` option to `PolygonLayer` for enabling MSAA antialiasing on polygon fills.
415423
- Added a new option, `enableAccessibilityLocationFallback`, to enable or disable reverse-geocoding API fallback for accessibility (screen reader).
416424

417425
#### Other changes (2.3.7)

articles/azure-maps/release-notes-spatial-module.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ services: azure-maps
1414

1515
This document contains information about new features and other changes to the Azure Maps Spatial IO Module.
1616

17-
## [0.1.8] (February 22 2024)
17+
## [0.1.8] (February 22, 2024)
1818

1919
### Bug fixes (0.1.8)
2020

articles/azure-maps/tutorial-search-location.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -155,6 +155,12 @@ The Map Control API is a convenient client library. This API allows you to easil
155155

156156
This section shows how to use the Maps [Search API] to find a point of interest on your map. It's a RESTful API designed for developers to search for addresses, points of interest, and other geographical information. The Search service assigns a latitude and longitude information to a specified address. The **Service Module** explained next can be used to search for a location using the Maps Search API.
157157

158+
> [!NOTE]
159+
>
160+
> **Azure Maps Web SDK Service Module retirement**
161+
>
162+
> The Azure Maps Web SDK Service Module is now deprecated and will be retired on 9/30/26. To avoid service disruptions, we recommend migrating to the Azure Maps JavaScript REST SDK by 9/30/26. For more information, see [JavaScript/TypeScript REST SDK Developers Guide (preview)](how-to-dev-guide-js-sdk.md).
163+
158164
### Service Module
159165

160166
1. In the map `ready` event handler, construct the search service URL by adding the following JavaScript code immediately after `map.layers.add(resultLayer);`:

articles/container-apps/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -148,6 +148,8 @@
148148
href: log-monitoring.md
149149
- name: Alerts
150150
href: alerts.md
151+
- name: OpenTelemetry agents
152+
href: opentelemetry-agents.md
151153
- name: Scaling & performance
152154
items:
153155
- name: Overview

0 commit comments

Comments
 (0)