You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory-domain-services/migrate-from-classic-vnet.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ ms.service: active-directory
8
8
ms.subservice: domain-services
9
9
ms.workload: identity
10
10
ms.topic: how-to
11
-
ms.date: 01/29/2023
11
+
ms.date: 03/10/2023
12
12
ms.author: justinha
13
13
---
14
14
@@ -174,11 +174,11 @@ Before you begin the migration process, complete the following initial checks an
174
174
175
175
The following network security group Inbound rules are required for the managed domain to provide authentication and management services. Don't edit or delete these network security group rules for the virtual network subnet your managed domain is deployed into.
176
176
177
-
|Inbound port number | Protocol | Source | Destination | Action | Required | Purpose |
Make a note of this target resource group, target virtual network, and target virtual network subnet. These resource names are used during the migration process.
# Validation differences by supported account types (signInAudience)
17
17
18
-
When registering an application with the Microsoft identity platform for developers, you're asked to select which account types your application supports. In the application object and manifest, this property is `signInAudience`.
18
+
When registering an application with the Microsoft identity platform for developers, you're asked to select which account types your application supports. You can refer to the **Help me choose** link under **Supported account types** during the registration process. The value you select for this property has implications on other app object properties.
19
19
20
-
The options include the following values:
20
+
After the application has been registered, you can check or change the account type that the application supports at any time. Under the **Manage** pane of your application, search for **Manifest** and find the `signInAudience` value. The different account types, and the corresponding `signInAudience` are shown in the following table:
21
21
22
-
-**AzureADMyOrg**: Only accounts in the organizational directory where the app is registered (single-tenant).
23
-
-**AzureADMultipleOrgs**: Accounts in any organizational directory (multi-tenant).
24
-
-**AzureADandPersonalMicrosoftAccount**: Accounts in any organizational directory (multi-tenant) and personal Microsoft accounts (for example, Skype, Xbox, and Outlook.com).
22
+
| Supported account types (Register an application) |`signInAudience` (Manifest) |
| Accounts in this organizational directory only (Single tenant) |`AzureADMyOrg`|
25
+
| Accounts in any organizational directory (Any Azure AD directory - Multitenant) |`AzureADMultipleOrgs`|
26
+
| Accounts in any organizational directory (Any Azure AD directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox) |`AzureADandPersonalMicrosoftAccount`|
25
27
26
-
For registered applications, you can find the value for supported account types on the **Authentication** section of an application. You can also find it under the `signInAudience` property in the **Manifest**.
28
+
If you change this property you may need to change other properties first.
27
29
28
-
The value you select for this property has implications on other app object properties. As a result, if you change this property you may need to change other properties first.
30
+
## Validation differences
29
31
30
32
See the following table for the validation differences of various properties for different supported account types.
Copy file name to clipboardExpand all lines: articles/app-service/includes/quickstart-java/quickstart-java-linux-maven-pivot.md
+33-26Lines changed: 33 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,19 +39,23 @@ If Maven isn't your preferred development tool, check out our similar tutorials
39
39
40
40
# [Java SE](#tab/javase)
41
41
42
-
Clone the [Spring Boot Getting Started](https://github.com/spring-guides/gs-spring-boot) sample project and check out the source code that runs with this version of the article.
42
+
Clone the [sample project](https://github.com/Azure-Samples/app-service-java-quickstart) and check out the source code that runs with this version of the article.
Change directory to the completed project and build from the top level. Then `cd` to the subdirectory for petstore.
78
82
79
83
```azurecli-interactive
80
-
cd agoncal-application-petstore-ee7
84
+
cd app-service-java-quickstart
85
+
git checkout 20230308
86
+
mvn clean install
87
+
cd petstore-ee7
81
88
```
82
89
83
90
---
@@ -88,45 +95,47 @@ cd agoncal-application-petstore-ee7
88
95
> The Maven plugin supports **Java 17** and **Tomcat 10.0**. For more information about latest support, see [Java 17 and Tomcat 10.0 are available on Azure App Service](https://devblogs.microsoft.com/java/java-17-and-tomcat-10-0-available-on-azure-app-service/).
89
96
90
97
91
-
The deployment process to Azure App Service will use your Azure credentials from the Azure CLI automatically. If the Azure CLI is not installed locally, then the Maven plugin will authenticate with Oauth or device login. For more information, see [authentication with Maven plugins](https://github.com/microsoft/azure-maven-plugins/wiki/Authentication).
98
+
The deployment process to Azure App Service uses your Azure credentials from the Azure CLI automatically. If the Azure CLI isn't installed locally, then the Maven plugin authenticates with Oauth or device login. For more information, see [authentication with Maven plugins](https://github.com/microsoft/azure-maven-plugins/wiki/Authentication).
92
99
93
-
Run the Maven command below to configure the deployment. This command will help you to set up the App Service operating system, Java version, and Tomcat version.
100
+
Run the Maven command shown next to configure the deployment. This command helps you to set up the App Service operating system, Java version, and Tomcat version.
`<subscriptionId>` | false | Specify the subscription ID. | 0.1.0+
198
208
`<resourceGroup>` | true | Azure Resource Group for your Web App. | 0.1.0+
199
209
`<appName>` | true | The name of your Web App. | 0.1.0+
200
-
`<region>` | false | Specifies the region where your Web App will be hosted; the default value is **centralus**. All valid regions at [Supported Regions](https://azure.microsoft.com/global-infrastructure/services/?products=app-service) section. | 0.1.0+
210
+
`<region>` | false | Specifies the region to host your Web App; the default value is **centralus**. All valid regions at [Supported Regions](https://azure.microsoft.com/global-infrastructure/services/?products=app-service) section. | 0.1.0+
201
211
`<pricingTier>` | false | The pricing tier for your Web App. The default value is **P1v2** for production workload, while **B2** is the recommended minimum for Java dev/test. For more information, see [App Service Pricing](https://azure.microsoft.com/pricing/details/app-service/linux/)| 0.1.0+
202
212
`<runtime>` | false | The runtime environment configuration. For more information, see [Configuration Details](https://github.com/microsoft/azure-maven-plugins/wiki/Azure-Web-App:-Configuration-Details). | 0.1.0+
203
213
`<deployment>` | false | The deployment configuration. For more information, see [Configuration Details](https://github.com/microsoft/azure-maven-plugins/wiki/Azure-Web-App:-Configuration-Details). | 0.1.0+
204
214
205
215
For the complete list of configurations, see the plugin reference documentation. All the Azure Maven Plugins share a common set of configurations. For these configurations see [Common Configurations](https://github.com/microsoft/azure-maven-plugins/wiki/Common-Configuration). For configurations specific to App Service, see [Azure Web App: Configuration Details](https://github.com/microsoft/azure-maven-plugins/wiki/Azure-Web-App:-Configuration-Details).
206
216
207
-
Be careful about the values of `<appName>` and `<resourceGroup>` (`helloworld-1590394316693` and `helloworld-1590394316693-rg` accordingly in the demo), they'll be used later.
217
+
Be careful about the values of `<appName>` and `<resourceGroup>` (`helloworld-1590394316693` and `helloworld-1590394316693-rg` accordingly in the demo), they are used later.
Once deployment is completed, your application will be ready at `http://<appName>.azurewebsites.net/` (`http://helloworld-1590394316693.azurewebsites.net` in the demo). Open the url with your local web browser, you should see
240
+
Once deployment is completed, your application is ready at `http://<appName>.azurewebsites.net/` (`http://helloworld-1590394316693.azurewebsites.net` in the demo). Open the url with your local web browser, you should see
231
241
232
242
# [Java SE](#tab/javase)
233
243
@@ -245,9 +255,6 @@ Once deployment is completed, your application will be ready at `http://<appName
245
255
246
256
**Congratulations!** You've deployed your first Java app to App Service.
247
257
248
-
> [!div class="nextstepaction"]
249
-
> [I ran into an issue](https://www.research.net/r/javae2e?tutorial=app-service-linux-quickstart&step=deploy)
250
-
251
258
## 5 - Clean up resources
252
259
253
260
In the preceding steps, you created Azure resources in a resource group. If you don't need the resources in the future, delete the resource group from portal, or by running the following command in the Cloud Shell:
0 commit comments