Skip to content

Commit b37da78

Browse files
committed
Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into tamram-0317
2 parents fd53d35 + 776a4a3 commit b37da78

File tree

135 files changed

+624
-276
lines changed

Some content is hidden

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

135 files changed

+624
-276
lines changed

articles/active-directory/fundamentals/whats-new.md

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.service: active-directory
1212
ms.subservice: fundamentals
1313
ms.workload: identity
1414
ms.topic: conceptual
15-
ms.date: 02/27/2020
15+
ms.date: 03/18/2020
1616
ms.author: mimart
1717
ms.reviewer: dhanyahk
1818
ms.custom: it-pro
@@ -36,7 +36,17 @@ This page is updated monthly, so revisit it regularly. If you're looking for ite
3636
---
3737

3838
## February 2020
39+
40+
### Upcoming changes to custom controls
41+
42+
**Type:** Plan for change
43+
**Service category:** MFA
44+
**Product capability:** Identity Security & Protection
3945

46+
We're planning to replace the current custom controls preview with an approach that allows partner-provided authentication capabilities to work seamlessly with the Azure Active Directory administrator and end user experiences. Today, partner MFA solutions face the following limitations: they work only after a password has been entered; they don’t serve as MFA for step-up authentication in other key scenarios; and they don’t integrate with end user or administrative credential management functions. The new implementation will allow partner-provided authentication factors to work alongside built-in factors for key scenarios, including registration, usage, MFA claims, step up authentication, reporting, and logging.
47+
48+
Custom controls will continue to be supported in preview alongside the new design until it reaches general availability. At that point, we'll give customers time to migrate to the new design. Because of the limitations of the current approach, we won't onboard new providers until the new design is available. We are working closely with customers and providers and will communicate the timeline as we get closer. [Learn more](https://docs.microsoft.com/azure/active-directory/conditional-access/controls).
49+
4050
### Identity Secure Score - MFA improvement action updates
4151

4252
**Type:** Plan for change

articles/active-directory/hybrid/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -316,6 +316,8 @@
316316
href: tshoot-connect-attribute-not-syncing.md
317317
- name: Installation issues
318318
href: tshoot-connect-install-issues.md
319+
- name: UPN changes
320+
href: howto-troubleshoot-upn-changes.md
319321
- name: Reference
320322
items:
321323
- name: Hybrid Identity Required Ports and Protocols

articles/active-directory/hybrid/howto-troubleshoot-upn-changes.md

Lines changed: 249 additions & 0 deletions
Large diffs are not rendered by default.
36.6 KB
Loading
932 KB
Loading
35.4 KB
Loading

articles/active-directory/saas-apps/paloaltoadmin-tutorial.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -114,6 +114,8 @@ To configure Azure AD single sign-on with Palo Alto Networks - Admin UI, perform
114114

115115
> [!NOTE]
116116
> These values are not real. Update these values with the actual Sign-On URL, Identifier and Reply URL. Contact [Palo Alto Networks - Admin UI Client support team](https://support.paloaltonetworks.com/support) to get these values. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
117+
>
118+
> Port 443 is required on the **Identifier** and the **Reply URL** as these values are hardcoded into the Palo Alto Firewall. Removing the port number will result in an error during login if removed.
117119

118120
5. Palo Alto Networks - Admin UI application expects the SAML assertions in a specific format. Configure the following claims for this application. You can manage the values of these attributes from the **User Attributes** section on application integration page. On the **Set up Single Sign-On with SAML** page, click **Edit** button to open **User Attributes** dialog.
119121

articles/active-directory/saas-apps/toc.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1666,7 +1666,7 @@
16661666
- name: Airstack
16671667
href: airstack-provisioning-tutorial.md
16681668
- name: Amazon Web Services (AWS) - Role Provisioning
1669-
href: amazon-web-service-tutorial.md#configure-azure-ad-single-sign-on
1669+
href: amazon-web-service-tutorial.md#configure-azure-ad-sso
16701670
- name: Asana
16711671
href: asana-provisioning-tutorial.md
16721672
- name: Atlassian Cloud

articles/advisor/toc.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@
3030
href: advisor-quick-fix.md
3131
- name: Advisor data in Azure Resource Graph
3232
href: advisor-azure-resource-graph.md
33-
- name: Get period summary for recommendations
33+
- name: Get periodic summary for recommendations
3434
href: advisor-recommendations-digest.md
3535
- name: Reference
3636
items:
Lines changed: 62 additions & 63 deletions
Original file line numberDiff line numberDiff line change
@@ -1,148 +1,147 @@
11
---
2-
title: 'QuickStart: Create a C# ASP.NET Core app'
2+
title: "Quickstart: Create a C# ASP.NET Core app"
33
description: Learn how to run web apps in Azure App Service by deploying the default C# ASP.NET Core web app template from Visual Studio.
44
ms.assetid: b1e6bd58-48d1-4007-9d6c-53fd6db061e3
55
ms.topic: quickstart
6-
ms.date: 08/30/2019
7-
ms.custom: mvc, devcenter, vs-azure
8-
ms.custom: seodec18
9-
6+
ms.date: 03/17/2020
7+
ms.custom: mvc, devcenter, vs-azure, seodec18
108
---
11-
# Create an ASP.NET Core web app in Azure
12-
13-
> [!NOTE]
14-
> This article deploys an app to App Service on Windows. To deploy to App Service on _Linux_, see [Create a .NET Core web app in App Service on Linux](./containers/quickstart-dotnetcore.md).
15-
>
169

17-
[Azure App Service](overview.md) provides a highly scalable, self-patching web hosting service.
10+
# Quickstart: Create an ASP.NET Core web app in Azure
1811

19-
This quickstart shows how to deploy your first ASP.NET Core web app to Azure App Service. When you're finished, you'll have a resource group that consists of an App Service plan and an App Service app with a deployed web application.
12+
In this quickstart, you'll learn how to create and deploy your first ASP.NET Core web app to [Azure App Service](overview.md).
2013

21-
[!INCLUDE [quickstarts-free-trial-note](../../includes/quickstarts-free-trial-note.md)]
14+
When you're finished, you'll have an Azure resource group consisting of an App Service hosting plan and an App Service with a deployed web application.
2215

2316
## Prerequisites
2417

25-
To complete this tutorial, install <a href="https://www.visualstudio.com/downloads/" target="_blank">Visual Studio 2019</a> with the **ASP.NET and web development** workload.
18+
- An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?ref=microsoft.com&utm_source=microsoft.com&utm_medium=docs&utm_campaign=visualstudio).
19+
- This quickstart deploys an app to App Service on Windows. To deploy to App Service on _Linux_, see [Create a .NET Core web app in App Service on Linux](./containers/quickstart-dotnetcore.md).
20+
- Install <a href="https://www.visualstudio.com/downloads/" target="_blank">Visual Studio 2019</a> with the **ASP.NET and web development** workload.
21+
22+
If you've installed Visual Studio 2019 already:
2623

27-
If you've installed Visual Studio 2019 already:
24+
- Install the latest updates in Visual Studio by selecting **Help** > **Check for Updates**.
25+
- Add the workload by selecting **Tools** > **Get Tools and Features**.
2826

29-
- Install the latest updates in Visual Studio by selecting **Help** > **Check for Updates**.
30-
- Add the workload by selecting **Tools** > **Get Tools and Features**.
3127

3228
## Create an ASP.NET Core web app
3329

34-
Create an ASP.NET Core web app by following these steps:
30+
Create an ASP.NET Core web app in Visual Studio by following these steps:
3531

36-
1. Open Visual Studio and then select **Create a new project**.
32+
1. Open Visual Studio and select **Create a new project**.
3733

38-
1. In **Create a new project**, find and choose **ASP.NET Core Web Application** for C#, then select **Next**.
34+
1. In **Create a new project**, select **ASP.NET Core Web Application** and confirm that **C#** is listed in the languages for that choice, then select **Next**.
3935

40-
1. In **Configure your new project**, name the application _myFirstAzureWebApp_, and then select **Create**.
36+
1. In **Configure your new project**, name your web application project *myFirstAzureWebApp*, and select **Create**.
4137

4238
![Configure your web app project](./media/app-service-web-get-started-dotnet/configure-web-app-project.png)
4339

44-
1. For this quickstart, choose the **Web Application** template. Make sure authentication is set to **No Authentication** and no other option is selected. Select **Create**.
45-
46-
![Select ASP.NET Core Razor Pages for this tutorial](./media/app-service-web-get-started-dotnet/aspnet-razor-pages-app.png)
47-
48-
You can deploy any type of ASP.NET Core web app to Azure.
40+
1. You can deploy any type of ASP.NET Core web app to Azure, but for this quickstart, choose the **Web Application** template. Make sure **Authentication** is set to **No Authentication**, and that no other option is selected. Then, select **Create**.
4941

50-
1. From the Visual Studio menu, select **Debug** > **Start Without Debugging** to run the web app locally.
42+
![Create a new ASP.NET Core web app](./media/app-service-web-get-started-dotnet/create-aspnet-core-web-app.png)
43+
44+
1. From the Visual Studio menu, select **Debug** > **Start Without Debugging** to run your web app locally.
5145

52-
![Run app locally](./media/app-service-web-get-started-dotnet/razor-web-app-running-locally.png)
46+
![Web app running locally](./media/app-service-web-get-started-dotnet/web-app-running-locally.png)
5347

5448
## Publish your web app
5549

56-
1. In **Solution Explorer**, right-click the **myFirstAzureWebApp** project and select **Publish**.
50+
To publish your web app, you must first create and configure a new App Service that you can publish your app to.
5751

58-
1. Choose **App Service** and then select **Publish**.
52+
As part of setting up the App Service, you'll create:
5953

60-
![Publish from project overview page](./media/app-service-web-get-started-dotnet/publish-app-vs2019.png)
54+
- A new [resource group](https://docs.microsoft.com/azure/azure-resource-manager/management/overview#terminology) to contain all of the Azure resources for the service.
55+
- A new [Hosting Plan](https://docs.microsoft.com/azure/app-service/overview-hosting-plans) that specifies the location, size, and features of the web server farm that hosts your app.
6156

62-
1. In **App Service Create new**, your options depend on whether you're signed in to Azure already and whether you have a Visual Studio account linked to an Azure account. Select either **Add an account** or **Sign in** to sign in to your Azure subscription. If you're already signed in, select the account you want.
57+
Follow these steps to create your App Service and publish your web app:
6358

64-
> [!NOTE]
65-
> If you're already signed in, don't select **Create** yet.
66-
>
59+
1. In **Solution Explorer**, right-click the **myFirstAzureWebApp** project and select **Publish**. If you haven't already signed-in to your Azure account from Visual Studio, select either **Add an account** or **Sign in**. You can also create a free Azure account.
6760

68-
![Sign in to Azure](./media/app-service-web-get-started-dotnet/sign-in-azure-vs2019.png)
61+
1. In the **Pick a publish target** dialog box, choose **App Service**, select **Create New**, and then select **Create Profile**.
6962

70-
[!INCLUDE [resource group intro text](../../includes/resource-group.md)]
63+
![Pick a publish target](./media/app-service-web-get-started-dotnet/pick-publish-target-vs2019.png)
7164

72-
1. For **Resource group**, select **New**.
65+
1. In the **App Service: Create new** dialog, provide a globally unique **Name** for your app by either accepting the default name, or entering a new name. Valid characters are: `a-z`, `A-Z`, `0-9`, and `-`. This **Name** is used as the URL prefix for your web app in the format `http://<app_name>.azurewebsites.net`.
7366

74-
1. In **New resource group name**, enter *myResourceGroup* and select **OK**.
67+
1. For **Subscription**, accept the subscription that is listed or select a new one from the drop-down list.
7568

76-
[!INCLUDE [app-service-plan](../../includes/app-service-plan.md)]
69+
1. In **Resource group**, select **New**. In **New resource group name**, enter *myResourceGroup* and select **OK**.
7770

78-
1. For the **Hosting Plan**, select **New**.
71+
1. For **Hosting Plan**, select **New**.
7972

80-
1. In the **Configure Hosting Plan** dialog, enter the values from the following table, and then select **OK**.
73+
1. In the **Hosting Plan: Create new** dialog, enter the values specified in the following table:
8174

82-
| Setting | Suggested Value | Description |
83-
|-|-|-|
84-
|App Service Plan| myAppServicePlan | Name of the App Service plan. |
85-
| Location | West Europe | The datacenter where the web app is hosted. |
86-
| Size | Free | [Pricing tier](https://azure.microsoft.com/pricing/details/app-service/?ref=microsoft.com&utm_source=microsoft.com&utm_medium=docs&utm_campaign=visualstudio) determines hosting features. |
75+
| Setting | Suggested Value | Description |
76+
| -------- | --------------- | ----------- |
77+
| **Hosting Plan** | *myFirstAzureWebAppPlan* | Name of the App Service plan. |
78+
| **Location** | *West Europe* | The datacenter where the web app is hosted. |
79+
| **Size** | *Free* | [Pricing tier](https://azure.microsoft.com/pricing/details/app-service/?ref=microsoft.com&utm_source=microsoft.com&utm_medium=docs&utm_campaign=visualstudio) determines hosting features. |
80+
81+
![Create new Hosting Plan](./media/app-service-web-get-started-dotnet/create-new-hosting-plan-vs2019.png)
8782

88-
![Create App Service plan](./media/app-service-web-get-started-dotnet/app-service-plan-vs2019.png)
83+
1. Leave **Application Insights** set to *None*.
8984

90-
1. In **Name**, enter a unique app name that includes only the valid characters are `a-z`, `A-Z`, `0-9`, and `-`. You can accept the automatically generated unique name. The URL of the web app is `http://<app_name>.azurewebsites.net`, where `<app_name>` is your app name.
85+
1. In the **App Service: Create new** dialog box, select **Create** to start creating the Azure resources.
9186

92-
![Configure app name](./media/app-service-web-get-started-dotnet/web-app-name-vs2019.png)
87+
![Create new app service](./media/app-service-web-get-started-dotnet/create-new-app-service-vs2019.png)
9388

94-
1. Select **Create** to start creating the Azure resources.
89+
1. Once the wizard completes, select **Publish**.
9590

96-
Once the wizard completes, it publishes the ASP.NET Core web app to Azure, and then launches the app in the default browser.
91+
![Publish web app to Azure](./media/app-service-web-get-started-dotnet/publish-web-app-vs2019.png)
9792

98-
![Published ASP.NET web app in Azure](./media/app-service-web-get-started-dotnet/web-app-running-live.png)
93+
Visual Studio publishes your ASP.NET Core web app to Azure, and launches the app in your default browser.
9994

100-
The app name specified in the **App Service Create new** page is used as the URL prefix in the format `http://<app_name>.azurewebsites.net`.
95+
![Published ASP.NET web app running in Azure](./media/app-service-web-get-started-dotnet/web-app-running-live.png)
10196

10297
**Congratulations!** Your ASP.NET Core web app is running live in Azure App Service.
10398

10499
## Update the app and redeploy
105100

101+
Follow these steps to update and redeploy your web app:
102+
106103
1. In **Solution Explorer**, under your project, open **Pages** > **Index.cshtml**.
107104

108105
1. Replace the two `<div>` tags with the following code:
109106

110107
```HTML
111108
<div class="jumbotron">
112109
<h1>ASP.NET in Azure!</h1>
113-
<p class="lead">This is a simple app that weve built that demonstrates how to deploy a .NET app to Azure App Service.</p>
110+
<p class="lead">This is a simple app that we've built that demonstrates how to deploy a .NET app to Azure App Service.</p>
114111
</div>
115112
```
116113

117114
1. To redeploy to Azure, right-click the **myFirstAzureWebApp** project in **Solution Explorer** and select **Publish**.
118115

119116
1. In the **Publish** summary page, select **Publish**.
120117

121-
![Visual Studio publishing summary page](./media/app-service-web-get-started-dotnet/publish-summary-page-vs2019.png)
118+
![Publish update to web app](./media/app-service-web-get-started-dotnet/publish-update-to-web-app-vs2019.png)
122119

123120
When publishing completes, Visual Studio launches a browser to the URL of the web app.
124121

125-
![Updated ASP.NET web app in Azure](./media/app-service-web-get-started-dotnet/web-app-running-live-updated.png)
122+
![Updated ASP.NET web app running in Azure](./media/app-service-web-get-started-dotnet/updated-web-app-running-live.png)
126123

127124
## Manage the Azure app
128125

129-
To manage the web app, go to the [Azure portal](https://portal.azure.com), and search for and select **App Services**.
126+
To manage your web app, go to the [Azure portal](https://portal.azure.com), and search for and select **App Services**.
130127

131128
![Select App Services](./media/app-service-web-get-started-dotnet/app-services.png)
132129

133130
On the **App Services** page, select the name of your web app.
134131

135-
![Portal navigation to Azure app](./media/app-service-web-get-started-dotnet/access-portal-vs2019.png)
136-
137-
You see your web app's Overview page. Here, you can do basic management like browse, stop, start, restart, and delete.
132+
![Portal navigation to Azure app](./media/app-service-web-get-started-dotnet/select-app-service.png)
138133

139-
![App Service in Azure portal](./media/app-service-web-get-started-dotnet/web-app-general-vs2019.png)
134+
The **Overview** page for your web app, contains options for basic management like browse, stop, start, restart, and delete. The left menu provides further pages for configuring your app.
140135

141-
The left menu provides different pages for configuring your app.
136+
![App Service in Azure portal](./media/app-service-web-get-started-dotnet/web-app-overview-page.png)
142137

143138
[!INCLUDE [Clean-up section](../../includes/clean-up-section-portal.md)]
144139

145140
## Next steps
146141

142+
In this quickstart, you used Visual Studio to create and deploy an ASP.NET Core web app to Azure App Service.
143+
144+
Advance to the next article to learn how to create a .NET Core app and connect it to a SQL Database:
145+
147146
> [!div class="nextstepaction"]
148147
> [ASP.NET Core with SQL Database](app-service-web-tutorial-dotnetcore-sqldb.md)

0 commit comments

Comments
 (0)