Skip to content

Commit ee2d26b

Browse files
committed
Merging changes synced from https://github.com/MicrosoftDocs/azure-docs-pr (branch live)
2 parents bc215a5 + 668b348 commit ee2d26b

File tree

189 files changed

+1954
-1303
lines changed

Some content is hidden

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

189 files changed

+1954
-1303
lines changed

.openpublishing.redirection.json

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1701,6 +1701,26 @@
17011701
"redirect_url": "/azure/cognitive-services/bing-web-search/quickstarts/client-libraries?pivots=programming-language-python",
17021702
"redirect_document_id": false
17031703
},
1704+
{
1705+
"source_path": "articles/cognitive-services/Bing-Image-Search/image-search-sdk-quickstart.md",
1706+
"redirect_url": "/azure/cognitive-services/bing-image-search/quickstarts/client-libraries?pivots=programming-language-csharp",
1707+
"redirect_document_id": false
1708+
},
1709+
{
1710+
"source_path": "articles/cognitive-services/Bing-Image-Search/image-sdk-java-quickstart.md",
1711+
"redirect_url": "/azure/cognitive-services/bing-image-search/quickstarts/client-libraries?pivots=programming-language-java",
1712+
"redirect_document_id": false
1713+
},
1714+
{
1715+
"source_path": "articles/cognitive-services/Bing-Image-Search/image-search-sdk-node-quickstart.md",
1716+
"redirect_url": "/azure/cognitive-services/bing-image-search/quickstarts/client-libraries?pivots=programming-language-javascript",
1717+
"redirect_document_id": false
1718+
},
1719+
{
1720+
"source_path": "articles/cognitive-services/Bing-Image-Search/image-sdk-python-quickstart.md",
1721+
"redirect_url": "/azure/cognitive-services/bing-image-search/quickstarts/client-libraries?pivots=programming-language-python",
1722+
"redirect_document_id": false
1723+
},
17041724
{
17051725
"source_path": "articles/virtual-machines/linux/classic/rdma-cluster.md",
17061726
"redirect_url": "/azure/virtual-machines/linux/sizes-hpc#rdma-capable-instances",
@@ -6706,6 +6726,10 @@
67066726
"redirect_url": "/azure/logic-apps/logic-apps-using-sap-connector",
67076727
"redirect_document_id": true
67086728
},
6729+
{
6730+
"source_path": "articles/scheduler/get-started-portal.md",
6731+
"redirect_url": "/azure/scheduler/migrate-from-scheduler-to-logic-apps",
6732+
},
67096733
{
67106734
"source_path": "articles/connectors/connectors-create-api-googledrive.md",
67116735
"redirect_url": "https://docs.microsoft.com/connectors/googledrive/",

articles/active-directory/hybrid/how-to-connect-sync-feature-preferreddatalocation.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -180,7 +180,7 @@ The outbound synchronization rule permits the attribute value to flow from the m
180180
| sourceObjectType | EQUAL | User |
181181
| cloudMastered | NOTEQUAL | True |
182182

183-
Scoping filter determines which Azure AD objects this outbound synchronization rule is applied to. In this example, we use the same scoping filter from “Out to Azure AD – User Identity” OOB (out-of-box) synchronization rule. It prevents the synchronization rule from being applied to **User** objects that are not synchronized from on-premises Active Directory. You might need to tweak the scoping filter according to your Azure AD Connect deployment.
183+
Scoping filter determines which Azure AD objects this outbound synchronization rule is applied to. In this example, we use the same scoping filter from “Out to Azure AD – User Identity” OOB (out-of-box) synchronization rule. It prevents the synchronization rule from being applied to **User** objects that are not synchronized from an on-premises Active Directory. You might need to tweak the scoping filter according to your Azure AD Connect deployment.
184184

185185
6. Go to the **Transformation** tab, and implement the following transformation rule:
186186

@@ -255,7 +255,6 @@ It is now time to verify the configuration and enable it for your users.
255255
3. Using Exchange Online PowerShell, verify that the mailbox region has been set correctly.
256256
![Screenshot of Exchange Online PowerShell](./media/how-to-connect-sync-feature-preferreddatalocation/preferreddatalocation-mailboxregion.png)
257257
Assuming your tenant has been marked to be able to use this feature, the mailbox is moved to the correct geo. This can be verified by looking at the server name where the mailbox is located.
258-
4. To verify that this setting has been effective over many mailboxes, use the script in the [TechNet gallery](https://gallery.technet.microsoft.com/office/PowerShell-Script-to-a6bbfc2e). This script also has a list of the server prefixes of all Office 365 datacenters, and which geo it is located in. It can be used as a reference in the previous step to verify the location of the mailbox.
259258

260259
## Next steps
261260

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -104,7 +104,7 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
104104
| First Name | user.givenname |
105105
| Last Name | user.surname |
106106
| Email | user.mail |
107-
| Username | user.userprinicipalname |
107+
| Username | user.userprincipalname |
108108
| StudentID | < Student ID > |
109109

110110
> [!NOTE]

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -102,7 +102,7 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
102102

103103
b. From the **Transformation** list, select **ExtractMailPrefix()**.
104104

105-
c. From the **Parameter 1** list, select **user.userprinicipalname**.
105+
c. From the **Parameter 1** list, select **user.userprincipalname**.
106106

107107
d. Click **Save**.
108108

articles/active-directory/saas-apps/sap-fiori-tutorial.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -170,7 +170,7 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
170170

171171
1. In the **Transformation** list, select **ExtractMailPrefix()**.
172172

173-
1. In the **Parameter 1** list, select **user.userprinicipalname**.
173+
1. In the **Parameter 1** list, select **user.userprincipalname**.
174174

175175
1. Select **Save**.
176176

articles/active-directory/saas-apps/sap-netweaver-tutorial.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -175,7 +175,7 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
175175

176176
b. From the **Transformation** list, select **ExtractMailPrefix()**.
177177

178-
c. From the **Parameter 1** list, select **user.userprinicipalname**.
178+
c. From the **Parameter 1** list, select **user.userprincipalname**.
179179

180180
d. Click **Save**.
181181

articles/active-directory/user-help/multi-factor-authentication-end-user-troubleshoot.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.assetid: 8f3aef42-7f66-4656-a7cd-d25a971cb9eb
99
ms.workload: identity
1010
ms.service: active-directory
1111
ms.subservice: user-help
12-
ms.topic: troubleshooting
12+
ms.topic: conceptual
1313
ms.date: 02/20/2020
1414
ms.author: curtand
1515
ms.reviewer: kexia

articles/app-service/app-service-web-tutorial-connect-msi.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -122,6 +122,9 @@ In *Web.config*, working from the top of the file and make the following changes
122122

123123
- Find the connection string called `MyDbConnection` and replace its `connectionString` value with `"server=tcp:<server-name>.database.windows.net;database=<db-name>;UID=AnyString;Authentication=Active Directory Interactive"`. Replace _\<server-name>_ and _\<db-name>_ with your server name and database name.
124124

125+
> [!NOTE]
126+
> The SqlAuthenticationProvider you just registered is based on top of the AppAuthentication library you installed earlier. By default, it uses a system-assigned identity. To leverage a user-assigned identity, you will need to provide an additional configuration. Please see [connection string support](../key-vault/service-to-service-authentication.md#connection-string-support) for the AppAuthentication library.
127+
125128
That's every thing you need to connect to SQL Database. When debugging in Visual Studio, your code uses the Azure AD user you configured in [Set up Visual Studio](#set-up-visual-studio). You'll set up the SQL Database server later to allow connection from the managed identity of your App Service app.
126129

127130
Type `Ctrl+F5` to run the app again. The same CRUD app in your browser is now connecting to the Azure SQL Database directly, using Azure AD authentication. This setup lets you run database migrations from Visual Studio.
@@ -184,6 +187,9 @@ Type `Ctrl+F5` to run the app again. The same CRUD app in your browser is now co
184187

185188
Next, you configure your App Service app to connect to SQL Database with a system-assigned managed identity.
186189

190+
> [!NOTE]
191+
> While the instructions in this section are for a system-assigned identity, a user-assigned identity can just as easily be used. To do this. you would need the change the `az webapp identity assign command` to assign the desired user-assigned identity. Then, when creating the SQL user, make sure to use the name of the user-assigned identity resource rather than the site name.
192+
187193
### Enable managed identity on app
188194

189195
To enable a managed identity for your Azure app, use the [az webapp identity assign](/cli/azure/webapp/identity?view=azure-cli-latest#az-webapp-identity-assign) command in the Cloud Shell. In the following command, replace *\<app-name>*.
@@ -232,7 +238,7 @@ ALTER ROLE db_ddladmin ADD MEMBER [<identity-name>];
232238
GO
233239
```
234240

235-
*\<identity-name>* is the name of the managed identity in Azure AD. Since it's system-assigned, it's always the same as the name of your App Service app. To grant permissions for an Azure AD group, use the group's display name instead (for example, *myAzureSQLDBAccessGroup*).
241+
*\<identity-name>* is the name of the managed identity in Azure AD. If the identity is system-assigned, the name always the same as the name of your App Service app. To grant permissions for an Azure AD group, use the group's display name instead (for example, *myAzureSQLDBAccessGroup*).
236242

237243
Type `EXIT` to return to the Cloud Shell prompt.
238244

articles/app-service/app-service-web-tutorial-dotnetcore-sqldb.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ What you learn how to:
3636
To complete this tutorial:
3737

3838
* [Install Git](https://git-scm.com/)
39-
* [Install .NET Core](https://www.microsoft.com/net/core/)
39+
* [Install .NET Core SDK](https://dotnet.microsoft.com/download)
4040

4141
## Create local .NET Core app
4242

articles/app-service/toc.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@
3333
items:
3434
- name: .NET Core with SQL DB
3535
href: app-service-web-tutorial-dotnetcore-sqldb.md
36-
- name: .NET with SQL DB
36+
- name: .NET Framework with SQL DB
3737
href: app-service-web-tutorial-dotnet-sqldatabase.md
3838
- name: PHP with MySQL
3939
href: app-service-web-tutorial-php-mysql.md

0 commit comments

Comments
 (0)