Skip to content

Commit 11b0c0e

Browse files
committed
Merging changes synced from https://github.com/MicrosoftDocs/azure-docs-pr (branch live)
2 parents f989aa1 + b1e25a8 commit 11b0c0e

File tree

226 files changed

+509
-6648
lines changed

Some content is hidden

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

226 files changed

+509
-6648
lines changed

.openpublishing.redirection.json

Lines changed: 121 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -51734,6 +51734,126 @@
5173451734
"source_path": "articles/jenkins/jenkins-azure-vm-agents.md",
5173551735
"redirect_url": "/azure/developer/jenkins/scale-deployments-using-vm-agents",
5173651736
"redirect_document_id": false
51737+
},
51738+
{
51739+
"source_path": "articles/jenkins/index.yml",
51740+
"redirect_url": "/azure/developer/jenkins/",
51741+
"redirect_document_id": false
51742+
},
51743+
{
51744+
"source_path": "articles/terraform/terraform-backend.md",
51745+
"redirect_url": "/azure/developer/terraform/store-state-in-azure-storage",
51746+
"redirect_document_id": false
51747+
},
51748+
{
51749+
"source_path": "articles/terraform/terraform-cloud-shell.md",
51750+
"redirect_url": "/azure/developer/terraform/install-configure",
51751+
"redirect_document_id": false
51752+
},
51753+
{
51754+
"source_path": "articles/terraform/terraform-create-complete-vm.md",
51755+
"redirect_url": "/azure/developer/terraform/create-linux-virtual machine-with-infrastructure",
51756+
"redirect_document_id": false
51757+
},
51758+
{
51759+
"source_path": "articles/terraform/terraform-create-configuration.md",
51760+
"redirect_url": "/azure/developer/terraform/deploy-azure-cosmos-db-to-azure-container-instances",
51761+
"redirect_document_id": false
51762+
},
51763+
{
51764+
"source_path": "articles/terraform/terraform-create-k8s-cluster-with-aks-applicationgateway-ingress.md",
51765+
"redirect_url": "/azure/developer/terraform/create-k8s-cluster-with-aks-applicationgateway-ingress",
51766+
"redirect_document_id": false
51767+
},
51768+
{
51769+
"source_path": "articles/terraform/terraform-create-k8s-cluster-with-tf-and-aks.md",
51770+
"redirect_url": "/azure/developer/terraform/create-k8s-cluster-with-tf-and-aks",
51771+
"redirect_document_id": false
51772+
},
51773+
{
51774+
"source_path": "articles/terraform/terraform-create-vm-cluster-module.md",
51775+
"redirect_url": "/azure/developer/terraform/create-vm-cluster-module",
51776+
"redirect_document_id": false
51777+
},
51778+
{
51779+
"source_path": "articles/terraform/terraform-create-vm-cluster-with-infrastructure.md",
51780+
"redirect_url": "/azure/developer/terraform/create-vm-cluster-with-infrastructure",
51781+
"redirect_document_id": false
51782+
},
51783+
{
51784+
"source_path": "articles/terraform/terraform-create-vm-scaleset-network-disks-hcl.md",
51785+
"redirect_url": "/azure/developer/terraform/create-vm-scaleset-network-disks-hcl",
51786+
"redirect_document_id": false
51787+
},
51788+
{
51789+
"source_path": "articles/terraform/terraform-create-vm-scaleset-network-disks-using-packer-hcl.md",
51790+
"redirect_url": "/azure/developer/terraform/create-vm-scaleset-network-disks-using-packer-hcl",
51791+
"redirect_document_id": false
51792+
},
51793+
{
51794+
"source_path": "articles/terraform/terraform-hub-spoke-hub-network.md",
51795+
"redirect_url": "/azure/developer/terraform/hub-spoke-hub-network",
51796+
"redirect_document_id": false
51797+
},
51798+
{
51799+
"source_path": "articles/terraform/terraform-hub-spoke-hub-nva.md",
51800+
"redirect_url": "/azure/developer/terraform/hub-spoke-hub-nva",
51801+
"redirect_document_id": false
51802+
},
51803+
{
51804+
"source_path": "articles/terraform/terraform-hub-spoke-introduction.md",
51805+
"redirect_url": "/azure/developer/terraform/hub-spoke-introduction",
51806+
"redirect_document_id": false
51807+
},
51808+
{
51809+
"source_path": "articles/terraform/terraform-hub-spoke-on-prem.md",
51810+
"redirect_url": "/azure/developer/terraform/hub-spoke-on-prem",
51811+
"redirect_document_id": false
51812+
},
51813+
{
51814+
"source_path": "articles/terraform/terraform-hub-spoke-spoke-network.md",
51815+
"redirect_url": "/azure/developer/terraform/hub-spoke-spoke-network",
51816+
"redirect_document_id": false
51817+
},
51818+
{
51819+
"source_path": "articles/terraform/terraform-hub-spoke-validation.md",
51820+
"redirect_url": "/azure/developer/terraform/hub-spoke-validation",
51821+
"redirect_document_id": false
51822+
},
51823+
{
51824+
"source_path": "articles/terraform/terraform-install-configure.md",
51825+
"redirect_url": "/azure/developer/terraform/install-configure",
51826+
"redirect_document_id": false
51827+
},
51828+
{
51829+
"source_path": "articles/terraform/terraform-overview.md",
51830+
"redirect_url": "/azure/developer/terraform/overview",
51831+
"redirect_document_id": false
51832+
},
51833+
{
51834+
"source_path": "articles/terraform/terraform-slot-walkthru.md",
51835+
"redirect_url": "/azure/developer/terraform/provision-infrastructure-using-azure-deployment-slots",
51836+
"redirect_document_id": false
51837+
},
51838+
{
51839+
"source_path": "articles/terraform/terraform-vscode-extension.md",
51840+
"redirect_url": "/azure/developer/terraform/configure-vs-code-extension-for-terraform",
51841+
"redirect_document_id": false
51842+
},
51843+
{
51844+
"source_path": "articles/terraform/terraform-vscode-module-generator.md",
51845+
"redirect_url": "/azure/developer/terraform/create-a-base-template-using-yeoman",
51846+
"redirect_document_id": false
51847+
},
51848+
{
51849+
"source_path": "articles/terraform/terraform-modules.md",
51850+
"redirect_url": "/azure/developer/terraform/test-modules-using-terratest",
51851+
"redirect_document_id": false
51852+
},
51853+
{
51854+
"source_path": "articles/terraform/index",
51855+
"redirect_url": "/azure/developer/terraform/",
51856+
"redirect_document_id": false
5173751857
}
51738-
]
51858+
]
5173951859
}

articles/active-directory-b2c/code-samples.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -43,3 +43,9 @@ The following tables provide links to samples for applications including iOS, An
4343
| Sample | Description |
4444
|--------| ----------- |
4545
| [javascript-msal-singlepageapp](https://github.com/Azure-Samples/active-directory-b2c-javascript-msal-singlepageapp) | A single page application (SPA) calling a Web API. Authentication is done with Azure AD B2C by using MSAL.js. |
46+
47+
## SAML test application
48+
49+
| Sample | Description |
50+
|--------| ----------- |
51+
| [saml-sp-tester](https://github.com/azure-ad-b2c/saml-sp-tester/tree/master/source-code) | SAML test application to test Azure AD B2C configured to act as SAML identity provider. |

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

Lines changed: 14 additions & 9 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: 04/06/2020
16+
ms.date: 04/23/2020
1717
ms.author: mimart
1818
ms.reviewer: arvinh
1919

@@ -23,23 +23,28 @@ ms.collection: M365-identity-device-management
2323

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

26-
**Target audience:** This document is targeted towards developers building applications integrated with Azure AD. For others looking to integrate an existing application 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).
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).
2727

2828
**Common scenarios**
2929

30+
Azure AD provides an out of the box service for provisioning and an extensible platform to build your applications on. The decision tree outlines how a developer would use [SCIM](https://aka.ms/scimoverview) and the [Microsoft Graph](https://docs.microsoft.com/graph/overview) to automate provisioning.
31+
3032
> [!div class="checklist"]
3133
> * Automatically create users in my application
3234
> * Automatically remove users from my application when they shouldn't have access anymore
3335
> * Integrate my application with multiple identity providers for provisioning
34-
> * Enrich my application with data from Microsoft services such as Sharepoint, Outlook, and Office.
36+
> * Enrich my application with data from Microsoft services such as Teams, Outlook, and Office.
3537
> * Automatically create, update, and delete users and groups in Azure AD and Active Directory
3638
3739
![SCIM Graph decision tree](./media/user-provisioning/scim-graph.png)
3840

3941
## Scenario 1: Automatically create users in my app
40-
Today, IT admins manually create user accounts in my application each time someone needs access or periodically upload CSV files. The process is time consuming for customers and slows down adoption of my application. All I need is basic [user](https://docs.microsoft.com/graph/api/resources/user?view=graph-rest-1.0) information such as name, email, and userPrincipalName to create a user. Furthermore, my customers use various IdPs and I don't have the resources to maintain a sync engine and custom integrations with each IdP.
42+
Today, IT admins provision users by manually creating user accounts or periodically uploading CSV files into my application. The process is time consuming for customers and slows down adoption of my application. All I need is basic user information such as name, email, and userPrincipalName to create a user.
43+
44+
**Recommendation**:
45+
* 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.
46+
* 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.
4147

42-
**Recommendation**: 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, without having to maintain a sync engine. Check out the example request below for how a user would be created.
4348

4449
```json
4550
POST /Users
@@ -93,21 +98,21 @@ My application relies on groups for access to various resources, and customers w
9398

9499
**Recommendation:** Support a SCIM compliant /Groups [endpoint](https://aka.ms/scimreferencecode). The Azure AD provisioning service will take care of creating groups and managing membership updates in your application.
95100

96-
## Scenario 4: Enrich my app with data from Microsoft services such as Teams, Outlook, and OneDrive.
101+
## Scenario 4: Enrich my app with data from Microsoft services such as Teams, Outlook, and OneDrive
97102
My application is built into Microsoft Teams and relies on message data. In addition, we store files for users in OneDrive. How can I enrich my application with the data from these services and across Microsoft?
98103

99104
**Recommendation:** The [Microsoft Graph](https://docs.microsoft.com/graph/) is your entry point to access Microsoft data. Each workload exposes APIs with the data that you need. The Microsoft graph can be used along with [SCIM provisioning](https://docs.microsoft.com/azure/active-directory/app-provisioning/use-scim-to-provision-users-and-groups) for the scenarios above. You can use SCIM to provision basic user attributes into your application while calling into graph to get any other data that you need.
100105

101-
## Scenario 5: Track changes in Microsoft services such as Teams, Outlook, and Azure AD.
106+
## Scenario 5: Track changes in Microsoft services such as Teams, Outlook, and Azure AD
102107
I need to be able to track changes to Teams and Outlook messages and react to them in real time. How can I get these changes pushed to my application?
103108

104-
**Recommendation:** The Microsoft Graph provides [change notifications](https://docs.microsoft.com/graph/webhooks) and change tracking for various resources. Note the following limitations of change notifications:
109+
**Recommendation:** The Microsoft Graph provides [change notifications](https://docs.microsoft.com/graph/webhooks) and [change tracking](https://docs.microsoft.com/graph/delta-query-overview) for various resources. Note the following limitations of change notifications:
105110
- If an event receiver acknowledges an event, but fails to act on it for any reason, the event may be lost
106111
- If an event receiver acknowledges an event, but fails to act on it for any reason, the event may be lost
107112
- Change notifications don't always contain the [resource data](https://docs.microsoft.com/graph/webhooks-with-resource-data)
108113
For the reasons above, developers often use change notifications along with change tracking for synchronization scenarios.
109114

110-
## Scenario 6: Provision users and groups in Azure AD.
115+
## Scenario 6: Provision users and groups in Azure AD
111116
My application creates information about a user that customers need in Azure AD. This could be an HR application than manages hiring, a communications app that creates phone numbers for users, or some other app that generates data that would be valuable in Azure AD. How do I populate the user record in Azure AD with that data?
112117

113118
**Recommendation** The Microsoft graph exposes /Users and /Groups endpoints that you can integrate with today to provision users into Azure AD. Please note that Azure Active Directory doesn't support writing those users back into Active Directory.

articles/active-directory/develop/quickstart-v2-javascipt-auth-code.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ ROBOTS: NOINDEX
2323
> This feature is currently in preview. Previews are made available to you on the condition that you agree to the [supplemental terms of use](https://azure.microsoft.com/support/legal/preview-supplemental-terms/). Some aspects of this feature might change before general availability (GA).
2424
2525

26-
This quickstart uses MSAL.js 2.0 with the Authorization Code flow. To use MSAL.js 1.0 with the implicit flow, view [this quickstart](https://docs.microsoft.com/azure/active-directory/develop/quickstart-v2-javascript)
26+
This quickstart uses MSAL.js 2.0 with the Authorization Code flow. To use MSAL.js 1.0 with the implicit flow, view [this quickstart](https://docs.microsoft.com/azure/active-directory/develop/quickstart-v2-javascript).
2727

2828
In this quickstart, you use a code sample to learn how a JavaScript single-page application (SPA) can sign in users of personal accounts, work accounts, and school accounts. A JavaScript SPA can also get an access token to call the Microsoft Graph API or any web API. See [How the sample works](#how-the-sample-works) for an illustration.
2929

articles/active-directory/users-groups-roles/licensing-service-plan-reference.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,17 +5,17 @@ description: Identifier map to manage Azure Active Directory licensing in the Az
55
services: active-directory
66
keywords: Azure Active Directory licensing service plans
77
documentationcenter: ''
8-
author: ajayanti1
8+
author: kkern
99
manager: mtillman
1010
editor: ''
1111

1212
ms.service: active-directory
1313
ms.topic: article
1414
ms.workload: identity
1515
ms.subservice: users-groups-roles
16-
ms.date: 03/14/2020
17-
ms.author: arjay
18-
ms.reviewer: arjay
16+
ms.date: 04/27/2020
17+
ms.author: kakern
18+
ms.reviewer: kakern
1919
ms.custom: "it-pro;seo-update-azuread-jan"
2020
ms.collection: M365-identity-device-management
2121
#Aruna Jayanti is minding this reference until it can be automated

articles/azure-monitor/toc.yml

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -241,13 +241,15 @@
241241
displayname: aks, microservice, istio, service mesh, application monitoring, monitor kubernetes, monitor aks
242242
href: app/kubernetes.md
243243
- name: Standalone - any environment
244-
items:
244+
items:
245245
- name: Java (preview)
246-
href: app/java-in-process-agent.md
247-
- name: Java JVM configuration
248-
href: app/java-standalone-arguments.md
249-
- name: Java configuration options
250-
href: app/java-standalone-config.md
246+
items:
247+
- name: Overview
248+
href: app/java-in-process-agent.md
249+
- name: Configuration options
250+
href: app/java-standalone-config.md
251+
- name: JVM arguments setup
252+
href: app/java-standalone-arguments.md
251253
- name: On-Premises servers
252254
items:
253255
- name: ASP.NET

articles/azure-resource-manager/templates/deployment-tutorial-local-template.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -32,9 +32,7 @@ Templates are JSON files. To review/edit templates, you need a good JSON editor.
3232

3333
## Review template
3434

35-
The template used in this tutorial is similar to the template used in the [tutorial about Quickstart templates](template-tutorial-quickstart-template.md). If you are interested in creating the template, you can go through that tutorial. However it's not required for completing this tutorial.
36-
37-
The template deploys a storage account, app service plan, and web app.
35+
The template deploys a storage account, app service plan, and web app. If you are interested in creating the template, you can go through [tutorial about Quickstart templates](template-tutorial-quickstart-template.md). However it's not required for completing this tutorial.
3836

3937
:::code language="json" source="~/resourcemanager-templates/get-started-deployment/local-template/azuredeploy.json":::
4038

articles/azure-resource-manager/templates/template-deploy-what-if.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Template deployment what-if (Preview)
33
description: Determine what changes will happen to your resources before deploying an Azure Resource Manager template.
44
author: mumian
55
ms.topic: conceptual
6-
ms.date: 04/09/2020
6+
ms.date: 04/27/2020
77
ms.author: jgao
88
---
99
# ARM template deployment what-if operation (Preview)
@@ -17,7 +17,9 @@ You can use the what-if operation with the PowerShell commands or REST API opera
1717

1818
## Install PowerShell module
1919

20-
To use what-if in PowerShell, install a preview version of the Az.Resources module from the PowerShell gallery.
20+
To use what-if in PowerShell, you must have PowerShell Core (6.x or 7.x). If you have PowerShell 5.x or earlier, [update your version of PowerShell](/powershell/scripting/install/installing-powershell).
21+
22+
After making sure you have the correct version of PowerShell, install a preview version of the Az.Resources module from the PowerShell gallery.
2123

2224
### Install preview version
2325

0 commit comments

Comments
 (0)