Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into dirty-pr-release-msid-gtd-tutorial-web-app-redirect-json

cilwerner · cilwerner · commit f00b2f578c2f · 2023-03-31T11:26:41.000+01:00
diff --git a/articles/active-directory/external-identities/whats-new-docs.md b/articles/active-directory/external-identities/whats-new-docs.md
@@ -1,7 +1,7 @@
 ---
 title: "What's new in Azure Active Directory External Identities"
 description: "New and updated documentation for the Azure Active Directory External Identities."
-ms.date: 03/01/2023
+ms.date: 03/31/2023
 ms.service: active-directory
 ms.subservice: B2B
 ms.topic: reference
@@ -15,6 +15,17 @@ manager: CelesteDG
 
 Welcome to what's new in Azure Active Directory External Identities documentation. This article lists new docs that have been added and those that have had significant updates in the last three months. To learn what's new with the External Identities service, see [What's new in Azure Active Directory](../fundamentals/whats-new.md).
 
+## March 2023
+
+### Updated articles
+
+- [Invite internal users to B2B collaboration](invite-internal-users.md)
+- [Federation with SAML/WS-Fed identity providers for guest users](direct-federation.md)
+- [Add Azure Active Directory (Azure AD) as an identity provider for External Identities](azure-ad-account.md)
+- [Quickstart: Add a guest user with PowerShell](b2b-quickstart-invite-powershell.md)
+- [Billing model for Azure AD External Identities](external-identities-pricing.md)
+- [Tutorial: Enforce multi-factor authentication for B2B guest users](b2b-tutorial-require-mfa.md)
+
 ## February 2023
 
 ### Updated articles
@@ -35,13 +46,4 @@ Welcome to what's new in Azure Active Directory External Identities documentatio
 - [Add Facebook as an identity provider for External Identities](facebook-federation.md)
 - [Leave an organization as an external user](leave-the-organization.md)
 - [External Identities in Azure Active Directory](external-identities-overview.md)
-- [External Identities documentation](index.yml)
-
-## December 2022
-
-### Updated articles
-
-- [Azure Active Directory B2B collaboration invitation redemption](redemption-experience.md)
-- [Azure Active Directory B2B collaboration API and customization](customize-invitation-api.md)
-- [Azure Active Directory External Identities: What's new](whats-new-docs.md)
-- [Auditing and reporting a B2B collaboration user](auditing-and-reporting.md)
+- [External Identities documentation](index.yml)
diff --git a/articles/azure-maps/release-notes-map-control.md b/articles/azure-maps/release-notes-map-control.md
@@ -16,6 +16,31 @@ This document contains information about new features and other changes to the M
 
 ## v3 (preview)
 
+### [3.0.0-preview.6] (March 31, 2023)
+
+#### Installation (3.0.0-preview.6)
+
+The preview is available on [npm][3.0.0-preview.6] and CDN.
+
+- **NPM:** Refer to the instructions at [azure-maps-control@3.0.0-preview.6][3.0.0-preview.6]
+
+- **CDN:** Reference the following CSS and JavaScript in the `<head>` element of an HTML file:
+
+    ```html
+    <link href="https://atlas.microsoft.com/sdk/javascript/mapcontrol/3.0.0-preview.6/atlas.min.css" rel="stylesheet" />
+    <script src="https://atlas.microsoft.com/sdk/javascript/mapcontrol/3.0.0-preview.6/atlas.min.js"></script>
+    ```
+
+#### New features (3.0.0-preview.6)
+
+- Optimized the internal style transform performance.
+
+#### Bug fixes (3.0.0-preview.6)
+
+- Resolved an issue where the first style set request was unauthenticated for `AAD` authentication.
+
+- Eliminated redundant requests during map initialization and on style changed events.
+
 ### [3.0.0-preview.5] (March 15, 2023)
 
 #### Installation (3.0.0-preview.5)
@@ -176,6 +201,14 @@ This update is the first preview of the upcoming 3.0.0 release. The underlying [
 
 ## v2 (latest)
 
+### [2.2.6]
+
+#### Bug fixes (2.2.6)
+
+- Resolved an issue where the first style set request was unauthenticated for `AAD` authentication.
+
+- Eliminated redundant requests during map initialization and on style changed events.
+
 ### [2.2.5]
 
 #### New features (2.2.5)
@@ -241,11 +274,13 @@ Stay up to date on Azure Maps:
 > [!div class="nextstepaction"]
 > [Azure Maps Blog]
 
+[3.0.0-preview.6]: https://www.npmjs.com/package/azure-maps-control/v/3.0.0-preview.6
 [3.0.0-preview.5]: https://www.npmjs.com/package/azure-maps-control/v/3.0.0-preview.5
 [3.0.0-preview.4]: https://www.npmjs.com/package/azure-maps-control/v/3.0.0-preview.4
 [3.0.0-preview.3]: https://www.npmjs.com/package/azure-maps-control/v/3.0.0-preview.3
 [3.0.0-preview.2]: https://www.npmjs.com/package/azure-maps-control/v/3.0.0-preview.2
 [3.0.0-preview.1]: https://www.npmjs.com/package/azure-maps-control/v/3.0.0-preview.1
+[2.2.6]: https://www.npmjs.com/package/azure-maps-control/v/2.2.6
 [2.2.5]: https://www.npmjs.com/package/azure-maps-control/v/2.2.5
 [2.2.4]: https://www.npmjs.com/package/azure-maps-control/v/2.2.4
 [2.2.3]: https://www.npmjs.com/package/azure-maps-control/v/2.2.3
diff --git a/articles/private-link/disable-private-endpoint-network-policy.md b/articles/private-link/disable-private-endpoint-network-policy.md
@@ -18,7 +18,10 @@ By default, network policies are disabled for a subnet in a virtual network. To
 
 Network policies can be enabled either for Network Security Groups only, for User-Defined Routes only, or for both.
 
-If you enable network security policies for User-Defined Routes, the /32 routes that are generated by the private endpoint and propagated to all the subnets in its own VNet and directly peered VNets will be invalidated if you have User-Defined Routing, which is useful if you want all traffic (including traffic addressed to the private endpoint) to go through a firewall, since otherwise the /32 route would bypass any other route.
+If you enable network security policies for User-Defined Routes, the /32 routes that are generated by the private endpoint and propagated to all the subnets in its own VNet and directly peered VNets will be invalidated if you have User-Defined Routing, which is useful if you want all traffic (including traffic addressed to the private endpoint) to go through a firewall, since otherwise the /32 route would bypass any other route. 
+
+> [!NOTE]
+> Unless you configure a UDR, the Private Endpoint Route of /32 will remain active. And for the UDR to work on all private endpoints within the subnet, you need to enable PrivateEndpointNetworkPolicies.
 
 You can use the following to enable or disable the setting:
 
