Skip to content

Commit 645f338

Browse files
authored
Merge pull request #242970 from MicrosoftDocs/main
6/26/2023 10AM Publishing
2 parents 9d46b99 + 71de764 commit 645f338

File tree

76 files changed

+1777
-208
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

76 files changed

+1777
-208
lines changed

articles/active-directory-b2c/force-password-reset.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ manager: CelesteDG
99
ms.service: active-directory
1010
ms.workload: identity
1111
ms.topic: how-to
12-
ms.date: 10/06/2022
12+
ms.date: 06/26/2023
1313
ms.author: kengaderdus
1414
ms.subservice: B2C
1515
ms.custom: b2c-support
@@ -149,7 +149,7 @@ Once a password expiration policy has been set, you must also configure force pa
149149

150150
### Password expiry duration
151151

152-
The password expiry duration default value is **90** days. The value is configurable by using the [Set-MsolPasswordPolicy](/powershell/module/msonline/set-msolpasswordpolicy) cmdlet from the Azure Active Directory Module for Windows PowerShell. This command updates the tenant, so that all users' passwords expire after number of days you configure.
152+
By default, the password is set not to expire. However, the value is configurable by using the [Set-MsolPasswordPolicy](/powershell/module/msonline/set-msolpasswordpolicy) cmdlet from the Azure Active Directory Module for Windows PowerShell. This command updates the tenant, so that all users' passwords expire after number of days you configure.
153153

154154
## Next steps
155155

articles/active-directory/devices/concept-azure-ad-register.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ The goal of Azure AD registered - also known as Workplace joined - devices is to
4848

4949
Azure AD registered devices are signed in to using a local account like a Microsoft account on a Windows 10 or newer device. These devices have an Azure AD account for access to organizational resources. Access to resources in the organization can be limited based on that Azure AD account and Conditional Access policies applied to the device identity.
5050

51-
Administrators can secure and further control these Azure AD registered devices using Mobile Device Management (MDM) tools like Microsoft Intune. MDM provides a means to enforce organization-required configurations like requiring storage to be encrypted, password complexity, and security software kept updated.
51+
Administrators can further control these Azure AD registered devices by enrolling the device(s) into Mobile Device Management (MDM) tools like Microsoft Intune. MDM provides a means to enforce organization-required configurations like requiring storage to be encrypted, password complexity, and security software kept updated.
5252

5353
Azure AD registration can be accomplished when accessing a work application for the first time or manually using the Windows 10 or Windows 11 Settings menu.
5454

articles/app-service/environment/upgrade-to-asev3.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Take the first steps toward upgrading to App Service Environment v3
44
ms.author: jordanselig
55
author: seligj95
66
ms.topic: overview
7-
ms.date: 05/12/2023
7+
ms.date: 06/26/2023
88
---
99

1010
# Upgrade to App Service Environment v3
@@ -23,7 +23,7 @@ This page is your one-stop shop for guidance and resources to help you upgrade s
2323
|**2**|**Migrate**|Based on results of your review, either upgrade using the migration feature or follow the manual steps.<br><br>- [Use the automated migration feature](how-to-migrate.md)<br>- [Migrate manually](migration-alternatives.md)|
2424
|**3**|**Testing and troubleshooting**|Upgrading using the automated migration feature requires a 3-6 hour service window. Support teams are monitoring upgrades to ensure success. If you have a support plan and you need technical help, create a [support request](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest).|
2525
|**4**|**Optimize your App Service plans**|Once your upgrade is complete, you can optimize the App Service plans for additional benefits.<br><br>Review the autoselected Isolated v2 SKU sizes and scale up or scale down your App Service plans as needed.<br><br>- [Scale down your App Service plans](../manage-scale-up.md)<br>- [App Service Environment post-migration scaling guidance](migrate.md#pricing)<br><br>Check out the pricing estimates if needed.<br><br>- [App Service pricing page](https://azure.microsoft.com/pricing/details/app-service/windows/)<br>- [Azure pricing calculator](https://azure.microsoft.com/pricing/calculator)|
26-
|**5**|**Learn more**|Join the [free live webinar](https://msit.events.teams.microsoft.com/event/2c472562-426a-48d6-b963-21c73d6e6cb0@72f988bf-86f1-41af-91ab-2d7cd011db47) with FastTrack Architects.<br><br>Need more help? [Submit a request](https://cxp.azure.com/nominationportal/nominationform/fasttrack) to contact FastTrack.<br><br>[Frequently asked questions](migrate.md#frequently-asked-questions)<br><br>[Community support](https://aka.ms/asev1v2retirement)|
26+
|**5**|**Learn more**|Need more help? [Submit a request](https://cxp.azure.com/nominationportal/nominationform/fasttrack) to contact FastTrack.<br><br>[Frequently asked questions](migrate.md#frequently-asked-questions)<br><br>[Community support](https://aka.ms/asev1v2retirement)|
2727

2828
## Additional information
2929

articles/app-service/includes/quickstart-java/quickstart-java-linux-maven-pivot.md

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -231,6 +231,27 @@ mvn com.microsoft.azure:azure-webapp-maven-plugin:2.11.0:config
231231
232232
---
233233
234+
After you've confirmed your choices, the plugin adds the above plugin element and requisite settings to your project's `pom.xml` file that configure your web app to run in Azure App Service.
235+
236+
The relevant portion of the `pom.xml` file should look similar to the following example.
237+
238+
```xml-interactive
239+
<build>
240+
<plugins>
241+
<plugin>
242+
<groupId>com.microsoft.azure</groupId>
243+
<artifactId>>azure-webapp-maven-plugin</artifactId>
244+
<version>x.xx.x</version>
245+
<configuration>
246+
<schemaVersion>v2</schemaVersion>
247+
<resourceGroup>your-resourcegroup-name</resourceGroup>
248+
<appName>your-app-name</appName>
249+
...
250+
</configuration>
251+
</plugin>
252+
</plugins>
253+
</build>
254+
```
234255

235256
You can modify the configurations for App Service directly in your `pom.xml`. Some common configurations are listed below:
236257

articles/app-service/includes/quickstart-java/quickstart-java-windows-maven-pivot.md

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -156,6 +156,28 @@ JBoss EAP is only available on the Linux version of App Service. Select the **Li
156156
157157
---
158158
159+
After you've confirmed your choices, the plugin adds the above plugin element and requisite settings to your project's `pom.xml` file that configure your web app to run in Azure App Service.
160+
161+
The relevant portion of the `pom.xml` file should look similar to the following example.
162+
163+
```xml-interactive
164+
<build>
165+
<plugins>
166+
<plugin>
167+
<groupId>com.microsoft.azure</groupId>
168+
<artifactId>>azure-webapp-maven-plugin</artifactId>
169+
<version>x.xx.x</version>
170+
<configuration>
171+
<schemaVersion>v2</schemaVersion>
172+
<resourceGroup>your-resourcegroup-name</resourceGroup>
173+
<appName>your-app-name</appName>
174+
...
175+
</configuration>
176+
</plugin>
177+
</plugins>
178+
</build>
179+
```
180+
159181
You can modify the configurations for App Service directly in your `pom.xml`. Some common configurations are listed below:
160182

161183
Property | Required | Description | Version
-458 Bytes
Loading
31.9 KB
Loading

articles/app-service/overview-managed-identity.md

Lines changed: 16 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Managed identities
33
description: Learn how managed identities work in Azure App Service and Azure Functions, how to configure a managed identity and generate a token for a back-end resource.
44

55
ms.topic: article
6-
ms.date: 01/27/2022
6+
ms.date: 06/27/2023
77
ms.reviewer: yevbronsh,mahender
88
ms.custom: devx-track-csharp, devx-track-azurepowershell, devx-track-azurecli
99
---
@@ -13,14 +13,14 @@ ms.custom: devx-track-csharp, devx-track-azurepowershell, devx-track-azurecli
1313
This article shows you how to create a managed identity for App Service and Azure Functions applications and how to use it to access other resources.
1414

1515
> [!IMPORTANT]
16-
> Managed identities for App Service and Azure Functions won't behave as expected if your app is migrated across subscriptions/tenants. The app needs to obtain a new identity, which is done by [disabling](#remove) and re-enabling the feature. Downstream resources also need to have access policies updated to use the new identity.
16+
> Because [managed identities don't support cross-directory scenarios](../active-directory/managed-identities-azure-resources/managed-identities-faq.md#can-i-use-a-managed-identity-to-access-a-resource-in-a-different-directorytenant), they won't behave as expected if your app is migrated across subscriptions or tenants. To recreate the managed identities after such a move, see [Will managed identities be recreated automatically if I move a subscription to another directory?](../active-directory/managed-identities-azure-resources/managed-identities-faq.md#will-managed-identities-be-recreated-automatically-if-i-move-a-subscription-to-another-directory). Downstream resources also need to have access policies updated to use the new identity.
1717
1818
> [!NOTE]
1919
> Managed identities are not available for [apps deployed in Azure Arc](overview-arc-integration.md).
2020
2121
[!INCLUDE [app-service-managed-identities](../../includes/app-service-managed-identities.md)]
2222

23-
The managed identity configuration is specific to the slot. To configure a managed identity for a deployment slot in the portal, navigate to the slot first. To find the managed identity for your web app or deployment slot in your Azure Active Directory tenant from the Azure portal, search for it directly from the **Overview** page of your tenant. Usually, the slot name is similar to `<app name>/slots/<slot name>`.
23+
The managed identity configuration is specific to the slot. To configure a managed identity for a deployment slot in the portal, navigate to the slot first. To find the managed identity for your web app or deployment slot in your Azure Active Directory tenant from the Azure portal, search for it directly from the **Overview** page of your tenant. Usually, the slot name is similar to `<app-name>/slots/<slot-name>`.
2424

2525
## Add a system-assigned identity
2626

@@ -78,7 +78,7 @@ For example, a web app's template might look like the following JSON:
7878

7979
```json
8080
{
81-
"apiVersion": "2016-08-01",
81+
"apiVersion": "2022-03-01",
8282
"type": "Microsoft.Web/sites",
8383
"name": "[variables('appName')]",
8484
"location": "[resourceGroup().location]",
@@ -103,8 +103,8 @@ When the site is created, it has the following additional properties:
103103
```json
104104
"identity": {
105105
"type": "SystemAssigned",
106-
"tenantId": "<TENANTID>",
107-
"principalId": "<PRINCIPALID>"
106+
"tenantId": "<tenant-id>",
107+
"principalId": "<principal-id>"
108108
}
109109
```
110110

@@ -135,14 +135,13 @@ First, you'll need to create a user-assigned identity resource.
135135

136136
1. Select **Identity**.
137137

138-
1. Within the **User assigned** tab, click **Add**.
138+
1. Select **User assigned** > **Add**.
139139

140-
1. Search for the identity you created earlier and select it. Click **Add**.
140+
1. Search for the identity you created earlier, select it, and select **Add**.
141141

142142
![Managed identity in App Service](media/app-service-managed-service-identity/user-assigned-managed-identity-in-azure-portal.png)
143143

144-
> [!IMPORTANT]
145-
> If you select **Add** after you select a user-assigned identity to add, your application will restart.
144+
Once you select **Add**, the app restarts.
146145

147146
# [Azure CLI](#tab/cli)
148147

@@ -183,13 +182,13 @@ Adding a user-assigned identity in App Service is currently not supported.
183182
184183
An Azure Resource Manager template can be used to automate deployment of your Azure resources. To learn more about deploying to App Service and Functions, see [Automating resource deployment in App Service](../app-service/deploy-complex-application-predictably.md) and [Automating resource deployment in Azure Functions](../azure-functions/functions-infrastructure-as-code.md).
185184
186-
Any resource of type `Microsoft.Web/sites` can be created with an identity by including the following block in the resource definition, replacing `<RESOURCEID>` with the resource ID of the desired identity:
185+
Any resource of type `Microsoft.Web/sites` can be created with an identity by including the following block in the resource definition, replacing `<resource-id>` with the resource ID of the desired identity:
187186
188187
```json
189188
"identity": {
190189
"type": "UserAssigned",
191190
"userAssignedIdentities": {
192-
"<RESOURCEID>": {}
191+
"<resource-id>": {}
193192
}
194193
}
195194
```
@@ -203,7 +202,7 @@ For example, a web app's template might look like the following JSON:
203202

204203
```json
205204
{
206-
"apiVersion": "2016-08-01",
205+
"apiVersion": "2022-03-01",
207206
"type": "Microsoft.Web/sites",
208207
"name": "[variables('appName')]",
209208
"location": "[resourceGroup().location]",
@@ -233,9 +232,9 @@ When the site is created, it has the following additional properties:
233232
"identity": {
234233
"type": "UserAssigned",
235234
"userAssignedIdentities": {
236-
"<RESOURCEID>": {
237-
"principalId": "<PRINCIPALID>",
238-
"clientId": "<CLIENTID>"
235+
"<resource-id>": {
236+
"principalId": "<principal-id>",
237+
"clientId": "<client-id>"
239238
}
240239
}
241240
}
@@ -365,7 +364,7 @@ When you remove a system-assigned identity, it's deleted from Azure Active Direc
365364
1. Select **Identity**. Then follow the steps based on the identity type:
366365

367366
- **System-assigned identity**: Within the **System assigned** tab, switch **Status** to **Off**. Click **Save**.
368-
- **User-assigned identity**: Click the **User assigned** tab, select the checkbox for the identity, and click **Remove**. Click **Yes** to confirm.
367+
- **User-assigned identity**: Select the **User assigned** tab, select the checkbox for the identity, and select **Remove**. Select **Yes** to confirm.
369368

370369
# [Azure CLI](#tab/cli)
371370

articles/azure-maps/choose-map-style.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ map.setStyle({
3838
});
3939
```
4040
41-
For a fully functional sample that shows how the different styles affect how the map is rendered, see [Map style options] in the [Azure Maps Samples].
41+
For a fully functional sample that shows how the different styles affect how the map is rendered, see [Map style options] in the [Azure Maps Samples]. For the source code for this sample, see [Map style options source code].
4242
4343
<!-----------------------------------------------------------------------------------------------
4444
<br/>
@@ -170,4 +170,5 @@ See the following articles for more code samples to add to your maps:
170170
[Add a symbol layer]: map-add-pin.md
171171
[Add a bubble layer]: map-add-bubble-layer.md
172172
[Map style options]: https://samples.azuremaps.com/map/map-style-options
173+
[Map style options source code]: https://github.com/Azure-Samples/AzureMapsCodeSamples/blob/main/Samples/Map/Map%20style%20options/Map%20style%20options.html
173174
[Azure Maps Samples]: https://samples.azuremaps.com

0 commit comments

Comments
 (0)