Skip to content

Commit 227ec51

Browse files
committed
Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into troubleshoot-runbooks
2 parents 8eafe30 + d83fd0e commit 227ec51

File tree

454 files changed

+8693
-6012
lines changed

Some content is hidden

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

454 files changed

+8693
-6012
lines changed

.openpublishing.redirection.json

Lines changed: 85 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,20 @@
11
{
22
"redirections": [
3+
{
4+
"source_path": "articles/openshift/howto-azure-monitor-v4.md",
5+
"redirect_url": "articles/azure-monitor/insights/container-insights-azure-redhat4-setup.md",
6+
"redirect_document_id": false
7+
},
8+
{
9+
"source_path": "articles/openshift/tutorial-scale-cluster.md",
10+
"redirect_url": "articles/openshift/tutorial-connect-cluster.md",
11+
"redirect_document_id": false
12+
},
13+
{
14+
"source_path": "articles/openshift/howto-using-azure-redhat-openshift.md",
15+
"redirect_url": "articles/openshift/tutorial-create-cluster.md",
16+
"redirect_document_id": false
17+
},
318
{
419
"source_path": "articles/virtual-network/create-virtual-network-classic.md",
520
"redirect_url": "/previous-versions/azure/virtual-network/create-virtual-network-classic",
@@ -592,6 +607,46 @@
592607
"redirect_url": "/azure/virtual-machines/workloads/oracle/oracle-overview/",
593608
"redirect_document_id": false
594609
},
610+
{
611+
"source_path": "articles/machine-learning/studio/use-case-excel-studio.md",
612+
"redirect_url": "/azure/machine-learning/studio/",
613+
"redirect_document_id": false
614+
},
615+
{
616+
"source_path": "articles/machine-learning/studio/azure-ml-customer-churn-scenario.md",
617+
"redirect_url": "/azure/machine-learning/studio/",
618+
"redirect_document_id": false
619+
},
620+
{
621+
"source_path": "articles/machine-learning/studio/text-analytics-module-tutorial.md",
622+
"redirect_url": "/azure/machine-learning/studio/",
623+
"redirect_document_id": false
624+
},
625+
{
626+
"source_path": "articles/machine-learning/studio/extend-your-experiment-with-r.md",
627+
"redirect_url": "/azure/machine-learning/studio/",
628+
"redirect_document_id": false
629+
},
630+
{
631+
"source_path": "articles/machine-learning/studio/debug-models.md",
632+
"redirect_url": "/azure/machine-learning/studio/",
633+
"redirect_document_id": false
634+
},
635+
{
636+
"source_path": "articles/machine-learning/studio/troubleshooting-creating-ml-workspace.md",
637+
"redirect_url": "/azure/machine-learning/studio/",
638+
"redirect_document_id": false
639+
},
640+
{
641+
"source_path": "articles/machine-learning/studio/basics-infographic-with-algorithm-examples.md",
642+
"redirect_url": "/azure/machine-learning/how-to-select-algorithms",
643+
"redirect_document_id": false
644+
},
645+
{
646+
"source_path": "articles/machine-learning/studio/convert-training-experiment-to-scoring-experiment.md",
647+
"redirect_url": "/azure/machine-learning/studio/deploy-a-machine-learning-web-service",
648+
"redirect_document_id": false
649+
},
595650
{
596651
"source_path": "articles/machine-learning/studio/consume-web-service-with-web-app-template.md",
597652
"redirect_url": "/azure/machine-learning/studio/consume-web-services",
@@ -2352,6 +2407,16 @@
23522407
"redirect_url": "/azure/cosmos-db/conflict-resolution-policies",
23532408
"redirect_document_id": true
23542409
},
2410+
{
2411+
"source_path": "articles/cosmos-db/provision-throughput-autopilot.md",
2412+
"redirect_url": "/azure/cosmos-db/provision-throughput-autoscale",
2413+
"redirect_document_id": true
2414+
},
2415+
{
2416+
"source_path": "articles/cosmos-db/autopilot-faq.md",
2417+
"redirect_url": "/azure/cosmos-db/autoscale-faq",
2418+
"redirect_document_id": true
2419+
},
23552420
{
23562421
"source_path": "articles/cosmos-db/how-to-custom-synchronization.md",
23572422
"redirect_url": "/azure/cosmos-db/how-to-multi-master",
@@ -2807,6 +2872,11 @@
28072872
"redirect_url": "https://github.com/Azure-Samples/active-directory-dotnet-native-uwp-v2",
28082873
"redirect_document_id": false
28092874
},
2875+
{
2876+
"source_path": "articles/active-directory/develop/quickstart-v2-javascipt-auth-code.md",
2877+
"redirect_url": "/azure/active-directory/develop/quickstart-v2-javascript-auth-code",
2878+
"redirect_document_id": true
2879+
},
28102880
{
28112881
"source_path": "articles/active-directory/develop/active-directory-v2-devquickstarts-wpf.md",
28122882
"redirect_url": "https://docs.microsoft.com/azure/active-directory/develop/guidedsetups/active-directory-windesktop",
@@ -7372,6 +7442,11 @@
73727442
"redirect_url": "/azure/logic-apps/logic-apps-using-sap-connector",
73737443
"redirect_document_id": true
73747444
},
7445+
{
7446+
"source_path": "articles/logic-apps/logic-apps-schema-2015-08-01.md",
7447+
"redirect_url": "/azure/logic-apps/logic-apps-schema-2016-04-01",
7448+
"redirect_document_id": true
7449+
},
73757450
{
73767451
"source_path": "articles/scheduler/get-started-portal.md",
73777452
"redirect_url": "/azure/scheduler/migrate-from-scheduler-to-logic-apps"
@@ -32066,6 +32141,16 @@
3206632141
"redirect_url": "/azure/api-management/mock-api-responses",
3206732142
"redirect_document_id": false
3206832143
},
32144+
{
32145+
"source_path": "articles/api-management/api-management-howto-deploy-self-hosted-gateway-to-k8s.md",
32146+
"redirect_url": "/azure/api-management/how-to-deploy-self-hosted-gateway-kubernetes",
32147+
"redirect_document_id": false
32148+
},
32149+
{
32150+
"source_path": "articles/api-management/api-management-howto-deploy-self-hosted-gateway-to-docker.md",
32151+
"redirect_url": "/azure/api-management/how-to-deploy-self-hosted-gateway-docker",
32152+
"redirect_document_id": false
32153+
},
3206932154
{
3207032155
"source_path": "articles/container-service/kubernetes/container-service-deploy-spring-boot-app-on-kubernetes.md",
3207132156
"redirect_url": "/java/azure/spring-framework/deploy-spring-boot-java-app-on-kubernetes",

articles/active-directory/app-provisioning/application-provisioning-quarantine-status.md

Lines changed: 9 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.workload: identity
1313
ms.tgt_pltfrm: na
1414
ms.devlang: na
1515
ms.topic: conceptual
16-
ms.date: 10/03/2019
16+
ms.date: 04/28/2020
1717
ms.author: mimart
1818
ms.reviewer: arvinh
1919

@@ -30,7 +30,7 @@ While in quarantine, the frequency of incremental cycles is gradually reduced to
3030

3131
There are three ways to check whether an application is in quarantine:
3232

33-
- In the Azure portal, navigate to **Azure Active Directory** > **Enterprise applications** > <*application name*> > **Provisioning** and scroll to the progress bar at the bottom.
33+
- In the Azure portal, navigate to **Azure Active Directory** > **Enterprise applications** > <*application name*> > **Provisioning** and review the progress bar for a quarantine message.
3434

3535
![Provisioning status bar showing quarantine status](./media/application-provisioning-quarantine-status/progress-bar-quarantined.png)
3636

@@ -48,7 +48,13 @@ There are three ways to check whether an application is in quarantine:
4848

4949
## Why is my application in quarantine?
5050

51-
A Microsoft Graph request to get the status of the provisioning job shows the following reason for quarantine:
51+
|Description|Recommended Action|
52+
|---|---|
53+
|**SCIM Compliance issue:** An HTTP/404 Not Found response was returned rather than the expected HTTP/200 OK response. In this case the Azure AD provisioning service has made a request to the target application and received an unexpected response.|Check the admin credentials section to see if the application requires specifying the tenant URL and ensure that the URL is correct. If you don't see an issue, please contact the application developer to ensure that their service is SCIM-compliant. https://tools.ietf.org/html/rfc7644#section-3.4.2 |
54+
|**Invalid credentials:** When attempting to authorize access to the target application we received a response from the target application that indicates the credentials provided are invalid.|Please navigate to the admin credentials section of the provisioning configuration UI and authorize access again with valid credentials. If the application is in the gallery, review the application configuration tutorial for any additional steps required.|
55+
|**Duplicate roles:** Roles imported from certain applications like Salesforce and Zendesk must be unique. |Navigate to the application [manifest](https://docs.microsoft.com/azure/active-directory/develop/reference-app-manifest) in the Azure portal and remove the duplicate role.|
56+
57+
A Microsoft Graph request to get the status of the provisioning job shows the following reason for quarantine:
5258

5359
- `EncounteredQuarantineException` indicates that invalid credentials were provided. The provisioning service is unable to establish a connection between the source system and the target system.
5460

articles/active-directory/app-provisioning/scim-graph-scenarios.md

Lines changed: 3 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,29 +1,23 @@
11
---
2-
title: Using SCIM, the Microsoft Graph, and the Azure AD provisioning service to provision users and enrich your application with the data it needs | Microsoft Docs
2+
title: Use SCIM, Microsoft Graph, and Azure AD to provision users and enrich apps with data
33
description: Using SCIM and the Microsoft Graph together to provision users and enrich your application with the data it needs .
44
services: active-directory
5-
documentationcenter: ''
65
author: msmimart
76
manager: CelesteDG
8-
9-
ms.assetid:
107
ms.service: active-directory
118
ms.subservice: app-provisioning
129
ms.workload: identity
13-
ms.tgt_pltfrm: na
14-
ms.devlang: na
1510
ms.topic: conceptual
16-
ms.date: 04/23/2020
11+
ms.date: 04/26/2020
1712
ms.author: mimart
1813
ms.reviewer: arvinh
1914

20-
ms.collection: M365-identity-device-management
2115
---
2216

2317

2418
# Using SCIM and Microsoft Graph together to provision users and enrich your application with the data it needs
2519

26-
**Target audience:** This document is targeted towards developers building applications to be integrated with Azure AD. For others looking to use applications already integrated with Azure AD, such as Zoom, ServiceNow, and DropBox, you can skip this and review the application specific [tutorials](https://docs.microsoft.com/azure/active-directory/saas-apps/tutorial-list) or review [how the provisioning service works](https://docs.microsoft.com/azure/active-directory/app-provisioning/how-provisioning-works).
20+
**Target audience:** This article is targeted towards developers building applications to be integrated with Azure Active Directory (Azure AD). If you're looking to use applications already integrated with Azure AD, such as Zoom, ServiceNow, and DropBox, you can skip this article and review the application specific [tutorials](https://docs.microsoft.com/azure/active-directory/saas-apps/tutorial-list) or review [how the provisioning service works](https://docs.microsoft.com/azure/active-directory/app-provisioning/how-provisioning-works).
2721

2822
**Common scenarios**
2923

@@ -45,7 +39,6 @@ Today, IT admins provision users by manually creating user accounts or periodica
4539
* If your customers use various IdPs and you do not want to maintain a sync engine to integrate with each, support a SCIM compliant [/Users](https://aka.ms/scimreferencecode) endpoint. Your customers will be able to easily use this endpoint to integrate with the Azure AD provisioning service and automatically create user accounts when they need access. You can build the endpoint once and it will be compatible with all IdPs. Check out the example request below for how a user would be created using SCIM.
4640
* If you require user data found on the user object in Azure AD and other data from across Microsoft, consider building a SCIM endpoint for user provisioning and calling into the Microsoft Graph to get the rest of the data.
4741

48-
4942
```json
5043
POST /Users
5144
{

articles/active-directory/app-provisioning/use-scim-to-provision-users-and-groups.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -813,7 +813,7 @@ Requests from Azure Active Directory include an OAuth 2.0 bearer token. Any serv
813813

814814
In the token, the issuer is identified by an iss claim, like `"iss":"https://sts.windows.net/cbb1a5ac-f33b-45fa-9bf5-f37db0fed422/"`. In this example, the base address of the claim value, `https://sts.windows.net`, identifies Azure Active Directory as the issuer, while the relative address segment, _cbb1a5ac-f33b-45fa-9bf5-f37db0fed422_, is a unique identifier of the Azure Active Directory tenant for which the token was issued.
815815

816-
The audience for the token will be the application template ID for the application in the gallery, each of the applications registered in a single tenant may receive the same `iss` claim with SCIM requests. The application template ID for each application in the gallery varies, please contact [[email protected]](mailto:[email protected]) for questions around the application template ID for a gallery application. The application template ID for all custom apps is _8adf8e6e-67b2-4cf2-a259-e3dc5476c621_.
816+
The audience for the token will be the application template ID for the application in the gallery, each of the applications registered in a single tenant may receive the same `iss` claim with SCIM requests. The application template ID for all custom apps is _8adf8e6e-67b2-4cf2-a259-e3dc5476c621_. The token generated by the Azure AD provisioning service should only be used for testing. It should not be used in production environments.
817817

818818
In the sample code, requests are authenticated using the Microsoft.AspNetCore.Authentication.JwtBearer package. The following code enforces that requests to any of the service’s endpoints are authenticated using the bearer token issued by Azure Active Directory for a specified tenant:
819819

articles/active-directory/authentication/concept-authentication-passwordless.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -116,7 +116,7 @@ The following providers offer FIDO2 security keys of different form factors that
116116
| eWBM | [https://www.ewbm.com/support](https://www.ewbm.com/support) |
117117
| AuthenTrend | [https://authentrend.com/about-us/#pg-35-3](https://authentrend.com/about-us/#pg-35-3) |
118118
| Gemalto (Thales Group) | [https://safenet.gemalto.com/multi-factor-authentication/authenticators/passwordless-authentication/](https://safenet.gemalto.com/multi-factor-authentication/authenticators/passwordless-authentication/) |
119-
| OneSpan Inc. | [https://www.onespan.com/sites/default/files/2019-01/OneSpan-FIDO-Authentication.pdf](https://www.onespan.com/sites/default/files/2019-01/OneSpan-FIDO-Authentication.pdf) |
119+
| OneSpan Inc. | [https://www.onespan.com/products/fido](https://www.onespan.com/products/fido) |
120120
| IDmelon Technologies Inc. | [https://www.idmelon.com/#idmelon](https://www.idmelon.com/#idmelon) |
121121

122122
> [!NOTE]

articles/active-directory/authentication/tutorial-enable-sspr.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -103,7 +103,7 @@ To keep users informed about account activity, you can configure e-mail notifica
103103
If users need additional help with the SSPR process, you can customize the link for "Contact your administrator". This link is used in the SSPR registration process and when a user unlocks their account or resets their password. To make sure your users get the support needed, it's highly recommended to provide a custom helpdesk email or URL.
104104

105105
1. On the **Customization** page from the menu in the left-hand side, set *Customize helpdesk link* to **Yes**.
106-
1. In the **Custom helpdesk email or URL** field, provide an email address or web page URL where your users can get additional help from your organization, such as *https://support.contoso.com/*
106+
1. In the **Custom helpdesk email or URL** field, provide an email address or web page URL where your users can get additional help from your organization, such as *`https://support.contoso.com/`*
107107
1. To apply the custom link, select **Save**.
108108

109109
## Test self-service password reset

articles/active-directory/develop/TOC.yml

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -448,9 +448,13 @@
448448
- name: Automatic user provisioning (SCIM)
449449
items:
450450
- name: What is automatic user provisioning?
451-
href: /azure/active-directory/manage-apps/user-provisioning
452-
- name: Building and integrating a SCIM endpoint
453-
href: /azure/active-directory/manage-apps/use-scim-to-provision-users-and-groups
451+
href: /azure/active-directory/app-provisioning/user-provisioning
452+
- name: Develop and integrating a SCIM endpoint
453+
href: /azure/active-directory/app-provisioning/use-scim-to-provision-users-and-groups
454+
- name: Common provisioning scenarios
455+
href: /azure/active-directory/app-provisioning/scim-graph-scenarios
456+
- name: Automate configuration using MS Graph
457+
href: /azure/active-directory/app-provisioning/application-provisioning-configure-api
454458
- name: How-to guides
455459
items:
456460
- name: Authentication

articles/active-directory/develop/scenario-web-app-call-api-app-configuration.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ public void ConfigureServices(IServiceCollection services)
4646
{
4747
// more code here
4848
49-
services.AddSignIn(Configuration, "AzureAd");
49+
services.AddSignIn(Configuration, "AzureAd")
5050
.AddWebAppCallsProtectedWebApi(Configuration,
5151
initialScopes: new string[] { "user.read" })
5252
.AddInMemoryTokenCaches();

articles/active-directory/develop/tutorial-v2-aspnet-daemon-web-app.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -221,7 +221,7 @@ This project has web app and web API projects. To deploy them to Azure websites,
221221
1. Right-click the project in Solution Explorer, and then select **Publish**.
222222
1. Select **Import Profile** on the bottom bar, and import the publish profile that you downloaded earlier.
223223
1. Select **Configure**.
224-
1. On the **Connection** tab, update the destination URL so that it uses "https." For example, use [https://dotnet-web-daemon-v2-contoso.azurewebsites.net](https://dotnet-web-daemon-v2-contoso.azurewebsites.net). Select **Next**.
224+
1. On the **Connection** tab, update the destination URL so that it uses "https." For example, use `https://dotnet-web-daemon-v2-contoso.azurewebsites.net`. Select **Next**.
225225
1. On the **Settings** tab, make sure that **Enable Organizational Authentication** is cleared.
226226
1. Select **Save**. Select **Publish** on the main screen.
227227

0 commit comments

Comments
 (0)