Skip to content

Commit d614a9f

Browse files
authored
Merge pull request #98525 from MicrosoftDocs/master
12/10 AM Publish
2 parents 5ab4f7a + a5dca37 commit d614a9f

File tree

56 files changed

+569
-303
lines changed

Some content is hidden

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

56 files changed

+569
-303
lines changed

articles/active-directory/cloud-provisioning/how-to-configure.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ manager: daveba
77
ms.service: active-directory
88
ms.workload: identity
99
ms.topic: conceptual
10-
ms.date: 12/02/2019
10+
ms.date: 12/05/2019
1111
ms.subservice: hybrid
1212
ms.author: billmath
1313
ms.collection: M365-identity-device-management
@@ -27,8 +27,7 @@ To configure provisioning, use the following steps:
2727

2828
4. Click on **New configuration**.
2929
5. On the configuration screen, the on-premises domain is pre-populated
30-
6. Enter a **Notification email**. This email will be notified
31-
7. when provisioning is not healthy.
30+
6. Enter a **Notification email**. This email will be notified when provisioning is not healthy.
3231
8. Move the selector to **Enable** and click **Save**.
3332
![](media/tutorial-single-forest/configure2.png)
3433

articles/active-directory/cloud-provisioning/how-to-prerequisites.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ manager: daveba
77
ms.service: active-directory
88
ms.workload: identity
99
ms.topic: conceptual
10-
ms.date: 12/02/2019
10+
ms.date: 12/06/2019
1111
ms.subservice: hybrid
1212
ms.author: billmath
1313
ms.collection: M365-identity-device-management
@@ -43,7 +43,7 @@ The rest of the document will provide step-by-step instructions for these prereq
4343
| --- | --- |
4444
| **80** | Downloads the certificate revocation lists (CRLs) while validating the SSL certificate |
4545
| **443** | Handles all outbound communication with the service |
46-
| **8080** (optional) | Agents report their status every ten minutes over port 8080, if port 443 is unavailable. This status is displayed on the Azure AD portal. Port 8080 is _not_ used for user sign-ins. |
46+
| **8080** (optional) | Agents report their status every ten minutes over port 8080, if port 443 is unavailable. This status is displayed on the Azure AD portal. |
4747
4848
If your firewall enforces rules according to the originating users, open these ports for traffic from Windows services that run as a network service.
4949
- If your firewall or proxy allows you to specify safe suffixes, then add connections to **\*.msappproxy.net** and **\*.servicebus.windows.net**. If not, allow access to the [Azure datacenter IP ranges](https://www.microsoft.com/download/details.aspx?id=41653), which are updated weekly.

articles/active-directory/cloud-provisioning/reference-cloud-provisioning-faq.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ Yes. Cloud provisioning can be used to sync from multiple Active Directory fores
3636

3737
**Q: How is the agent updated?**
3838

39-
The agents are auto upgraded by Microsoft. This reduces the burden off IT to test and validate new agent versions.
39+
The agents are auto upgraded by Microsoft. For the IT team, this reduces the burden of having to test and validate new agent versions.
4040

4141
**Q: Can I disable auto upgrade?**
4242

articles/active-directory/develop/about-microsoft-identity-platform.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.service: active-directory
99
ms.subservice: develop
1010
ms.topic: overview
1111
ms.workload: identity
12-
ms.date: 06/03/2019
12+
ms.date: 12/09/2019
1313
ms.author: ryanwi
1414
ms.reviewer: agirling, saeeda, benv
1515
ms.custom: aaddev
@@ -23,13 +23,13 @@ Microsoft identity platform is an evolution of the Azure Active Directory (Azure
2323

2424
Up until now, most developers have worked with the Azure AD v1.0 platform to authenticate work and school accounts (provisioned by Azure AD) by requesting tokens from the Azure AD v1.0 endpoint, using Azure AD Authentication Library (ADAL), Azure portal for application registration and configuration, and Azure AD Graph API for programmatic application configuration.
2525

26-
With Microsoft identity platform (v2.0), expand your reach to these kinds of users:
26+
With the unified Microsoft identity platform (v2.0), you can write code once and authenticate any Microsoft identity into your application. For several platforms, the fully supported open-source Microsoft Authentication Library (MSAL) is recommended for use against the identity platform endpoints. MSAL is simple to use, provides great single sign-on (SSO) experiences for your users, helps you achieve high reliability and performance, and is developed using Microsoft Secure Development Lifecycle (SDL). When calling APIs, you can configure your application to take advantage of incremental consent, which allows you to delay the request for consent for more invasive scopes until the application’s usage warrants this at runtime. MSAL also supports Azure Active Directory B2C, so your customers use their preferred social, enterprise, or local account identities to get single sign-on access to your applications and APIs.
27+
28+
With Microsoft identity platform, expand your reach to these kinds of users:
2729

2830
- Work and school accounts (Azure AD provisioned accounts)
2931
- Personal accounts (such as Outlook.com or Hotmail.com)
30-
- Your customers who bring their own email or social identity (such as LinkedIn, Facebook, Google) via the Azure AD B2C offering
31-
32-
With the unified Microsoft identity platform, you can write code once and authenticate any Microsoft identity into your application. For several platforms, there’s a fully supported open-source library called Microsoft Authentication Library (MSAL). MSAL is simple to use, provides great single sign-on (SSO) experiences for your users, helps you achieve high reliability and performance, and is developed using Microsoft Secure Development Lifecycle (SDL). When calling APIs, you can configure your application to take advantage of incremental consent, which allows you to delay the request for consent for more invasive scopes until the application’s usage warrants this at runtime.
32+
- Your customers who bring their own email or social identity (such as LinkedIn, Facebook, Google) via MSAL and Azure AD B2C
3333

3434
You can use the Azure portal to register and configure your application, and use the Microsoft Graph API for programmatic application configuration.
3535

0 commit comments

Comments
 (0)