Skip to content

Commit cc347e2

Browse files
author
Trevor Bye
committed
fixing conflicts
2 parents ce92f11 + 40a5548 commit cc347e2

File tree

599 files changed

+46824
-45273
lines changed

Some content is hidden

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

599 files changed

+46824
-45273
lines changed

.openpublishing.redirection.json

Lines changed: 41438 additions & 41389 deletions
Large diffs are not rendered by default.

articles/active-directory-b2c/active-directory-b2c-custom-setup-adfs2016-idp.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,7 @@ This article shows you how to enable sign-in for an ADFS user account by using [
2323

2424
- Complete the steps in [Get started with custom policies in Azure Active Directory B2C](active-directory-b2c-get-started-custom.md).
2525
- Make sure that you have access to a certificate .pfx file with a private key. You can generate your own signed certificate and upload it to Azure AD B2C. Azure AD B2C uses this certificate to sign the SAML request sent to your SAML identity provider.
26+
- In order for Azure to accept the .pfx file password, the password must be encrypted with the TripleDES-SHA1 option in Windows Certificate Store Export utility as opposed to AES256-SHA256.
2627

2728
## Create a policy key
2829

articles/active-directory-b2c/active-directory-b2c-reference-audit-logs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ The **B2C** category in audit logs contains the following types of activities:
4040
> For user object CRUD activities, refer to the **Core Directory** category.
4141
4242
## Example activity
43-
The example below shows the data captured when a user signs in with an external identity provider:
43+
The example below shows the data captured when a user signs in with an external identity provider:
4444
![Example of Audit Log Activity Details page in Azure portal](./media/active-directory-b2c-reference-audit-logs/audit-logs-example.png)
4545

4646
The activity details panel contains the following relevant information:

articles/active-directory/conditional-access/TOC.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@
4242
href: plan-conditional-access.md
4343
- name: Best practices
4444
href: best-practices.md
45-
- name: Common policy templates
45+
- name: Common Conditional Access policies
4646
items:
4747
- name: Require MFA for administrators
4848
href: howto-conditional-access-policy-admin-mfa.md

articles/active-directory/fundamentals/active-directory-deployment-plans.md

Lines changed: 40 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -9,19 +9,16 @@ ms.service: active-directory
99
ms.subservice: fundamentals
1010
ms.workload: identity
1111
ms.topic: conceptual
12-
ms.date: 02/08/2019
12+
ms.date: 08/20/2019
1313
ms.author: ajburnle
1414
ms.custom: "it-pro, seodec18"
1515
ms.collection: M365-identity-device-management
1616
---
1717

1818
# Azure Active Directory deployment plans
19-
Looking for end-to-end guidance about how to deploy some of Azure Active Directory (Azure AD) capabilities? The following deployment plans walk through the business value, planning considerations, design, and operational procedures needed to successfully roll a few of the more common Azure AD capabilities.
20-
21-
Within the documents you will find e-mail templates, system architecture diagrams, common test cases, and more.
22-
23-
We'd love your feedback on the documents. Take this short [survey](https://aka.ms/deploymentplanfeedback) about how the documents worked for you.
19+
Looking for end-to-end guidance on deploying Azure Active Directory (Azure AD) capabilities? Azure AD deployment plans walk you through the business value, planning considerations, and operational procedures needed to successfully deploy common Azure AD capabilities.
2420

21+
From any of the plan pages, use your browser’s Print to PDF capability to create an up-to-date offline version of the documentation.
2522
## Include the right stakeholders
2623

2724
When beginning your deployment planning for a new capability, it’s important to include key stakeholders across your organization. We recommend that you identify and document the person or people who fulfill each of the following roles, and work with them to determine their involvement in the project.
@@ -46,23 +43,43 @@ Roles might include the following
4643
- **C**ontributor to project plan and outcome
4744

4845
- **I**nformed of project plan and outcome
49-
50-
## Deployment Plans
5146

5247

48+
## Deploy authentication
5349

54-
|Scenario |Description |
55-
|-|-|
56-
|[Multi-Factor Authentication](../authentication/howto-mfa-getstarted.md)|Azure Multi-Factor Authentication (MFA) is Microsoft's two-step verification solution. Using admin-approved authentication methods, Azure MFA helps safeguard your access to data and applications, while meeting the demand for a simple sign-in process.|
57-
|[Conditional Access](https://aka.ms/deploymentplans/ca)|With Conditional Access, you can implement automated access control decisions for who can access your cloud apps, based on conditions.|
58-
|[Self-service password reset](https://aka.ms/deploymentplans/sspr)|Self-service password reset helps your users reset their password, without administrator intervention, when and where they need to.|
59-
|[Privileged Identity Management](https://aka.ms/deploymentplans/pim)|Azure AD Privileged Identity Management (PIM) helps you manage privileged administrative roles across Azure AD, Azure resources, and other Microsoft Online Services. PIM provides solutions like just-in-time access, request approval workflows, and fully integrated access reviews so you can identify, uncover, and prevent malicious activities of privileged roles in real time.|
60-
|[Single sign-on](https://aka.ms/deploymentplans/sso)|Single sign-on helps you access all the apps and resources you need to do business, while signing in only once, using a single user account. After you've signed in, you can go from Microsoft Office to SalesForce, to Box without being required to authenticate (for example, type a password) a second time.|
61-
|[Seamless SSO](https://aka.ms/SeamlessSSODPDownload)|Azure Active Directory Seamless Single Sign-On (Azure AD Seamless SSO) automatically signs users in when they are on their corporate devices connected to your corporate network. After you turn on this feature, users won't need to type in their passwords to sign in to Azure AD, and usually, won't even need to type in their usernames. This feature provides your users easy access to your cloud-based applications without needing any additional on-premises components.|
62-
|[Access Panel](https://aka.ms/AccessPanelDPDownload)|Offer your users a simple hub to discover and access all their applications. Enable them to be more productive with self-service capabilities, such as the ability to request access to new apps and groups, or manage access to these resources on behalf of others.|
63-
|[ADFS to Password Hash Sync](https://aka.ms/deploymentplans/adfs2phs)|With Password Hash Synchronization, hashes of user passwords are synchronized from on-premises Active Directory to Azure AD, letting Azure AD to authenticate users with no interaction with the on-premises Active Directory|
64-
|[ADFS to Pass Through Authentication](https://aka.ms/deploymentplans/adfs2pta)|Azure AD Pass-through Authentication helps your users sign in to both on-premises and cloud-based applications, using the same passwords. This feature provides your users a better experience - one less password to remember, and reduces IT helpdesk costs because your users are less likely to forget how to sign in. When people sign in using Azure AD, this feature validates users' passwords directly against your on-premises Active Directory.|
65-
|[Azure AD Application Proxy](https://aka.ms/deploymentplans/appproxy)|Employees today want to be productive at any place, at any time, and from any device. They want to work on their own devices, whether they are tablets, phones, or laptops. And employees expect to be able to access all their applications, both SaaS apps in the cloud and corporate apps on-premises. Providing access to on-premises applications has traditionally involved virtual private networks (VPNs) or demilitarized zones (DMZs). Not only are these solutions complex and hard to make secure, but they are costly to set up and manage. There is a better way! - Azure AD Application Proxy|
66-
|[User provisioning](https://aka.ms/UserProvisioningDPDownload)|Azure AD helps you automate the creation, maintenance, and removal of user identities in cloud (SaaS) applications, such as Dropbox, Salesforce, ServiceNow, and more.|
67-
|[Workday-driven Inbound User Provisioning](https://aka.ms/WorkdayDeploymentPlan)|Workday-driven Inbound User Provisioning to Active Directory creates a foundation for ongoing identity governance and enhances the quality of business processes that rely on authoritative identity data. Using this feature, you can seamlessly manage the identity lifecycle of employees and contingent workers by configuring rules that map Joiner-Mover-Leaver processes (such as New Hire, Terminate, Transfer) to IT provisioning actions (such as Create, Enable, Disable, Delete accounts).|
68-
|[Reporting and Monitoring](https://aka.ms/deploymentplans/reporting)| The design of your Azure AD reporting and monitoring solution depends on your legal, security, and operational requirements as well as your existing environment and processes. This article presents the various design options and guides you to the right deployment strategy.|
50+
| Capability | Description|
51+
| -| -|
52+
| [Multi-Factor Authentication](https://docs.microsoft.com/en-us/azure/active-directory/authentication/howto-mfa-getstarted)| Azure Multi-Factor Authentication (MFA) is Microsoft's two-step verification solution. Using admin-approved authentication methods, Azure MFA helps safeguard access to your data and applications while meeting the demand for a simple sign-in process. |
53+
| [Conditional Access](https://aka.ms/deploymentplans/ca)| With Conditional Access, you can implement automated access control decisions for who can access your cloud apps, based on conditions. |
54+
| [Self-service password reset](https://aka.ms/deploymentplans/sspr)| Self-service password reset helps your users reset their passwords without administrator intervention, when and where they need to. |
55+
56+
## Deploy application management
57+
58+
| Capability | Description|
59+
| -| - |
60+
| [Single sign-on](https://aka.ms/deploymentplans/sso)| Single sign-on helps your users access the apps and resources they need to do business while signing in only once. After they've signed in, they can go from Microsoft Office to SalesForce to Box to internal applications without being required to enter credentials a second time. |
61+
| [Access panel](https://aka.ms/deploymentplans/accesspanel)| Offer your users a simple hub to discover and access all their applications. Enable them to be more productive with self-service capabilities, like requesting access to apps and groups, or managing access to resources on behalf of others. |
62+
63+
64+
## Deploy hybrid scenarios
65+
66+
| Capability | Description|
67+
| -| -|
68+
| [ADFS to Password Hash Sync](https://aka.ms/deploymentplans/adfs2phs)| With Password Hash Synchronization, hashes of user passwords are synchronized from on-premises Active Directory to Azure AD, letting Azure AD authenticate users with no interaction with the on-premises Active Directory |
69+
| [ADFS to Pass Through Authentication](https://aka.ms/deploymentplans/adfs2pta)| Azure AD Pass-through Authentication helps your users sign in to both on-premises and cloud-based applications using the same passwords. This feature provides users with a better experience - one less password to remember - and reduces IT helpdesk costs because users are less likely to forget how to sign in. When people sign in using Azure AD, this feature validates users' passwords directly against your on-premises Active Directory. |
70+
| [Azure AD Application Proxy](https://aka.ms/deploymentplans/appproxy)| Employees today want to be productive at any place, at any time, and from any device. They need to access SaaS apps in the cloud and corporate apps on-premises. Azure AD Application proxy enables this robust access without costly and complex virtual private networks (VPNs) or demilitarized zones (DMZs). |
71+
| [Seamless SSO](https://aka.ms/SeamlessSSODPDownload)| Azure Active Directory Seamless Single Sign-On (Azure AD Seamless SSO) automatically signs users in when they are on their corporate devices connected to your corporate network. With this feature, users won't need to type in their passwords to sign in to Azure AD and usually won't need to enter their usernames. This feature provides authorized users with easy access to your cloud-based applications without needing any additional on-premises components. |
72+
73+
## Deploy user provisioning
74+
75+
| Capability | Description|
76+
| -| -|
77+
| [User provisioning](https://aka.ms/UserProvisioningDPDownload)| Azure AD helps you automate the creation, maintenance, and removal of user identities in cloud (SaaS) applications, such as Dropbox, Salesforce, ServiceNow, and more. |
78+
| [Workday-driven Inbound User Provisioning](https://aka.ms/WorkdayDeploymentPlan)| Workday-driven Inbound User Provisioning to Active Directory creates a foundation for ongoing identity governance and enhances the quality of business processes that rely on authoritative identity data. Using this feature, you can seamlessly manage the identity lifecycle of employees and contingent workers by configuring rules that map Joiner-Mover-Leaver processes (such as New Hire, Terminate, Transfer) to IT provisioning actions (such as Create, Enable, Disable) |
79+
80+
## Deploy governance and reporting
81+
82+
| Capability | Description|
83+
| -| -|
84+
| [Privileged Identity Management](https://aka.ms/deploymentplans/pim)| Azure AD Privileged Identity Management (PIM) helps you manage privileged administrative roles across Azure AD, Azure resources, and other Microsoft Online Services. PIM provides solutions like just-in-time access, request approval workflows, and fully integrated access reviews so you can identify, uncover, and prevent malicious activities of privileged roles in real time. |
85+
| [Reporting and Monitoring](https://aka.ms/deploymentplans/reporting)| The design of your Azure AD reporting and monitoring solution depends on your legal, security, and operational requirements as well as your existing environment and processes. This article presents the various design options and guides you to the right deployment strategy. |

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -110,7 +110,7 @@ For more information, see [What's new for authentication?](https://docs.microsof
110110

111111
Azure AD customers can now set policies to manage FIDO2 security keys for their organization's users and groups. End-users can also self-register their security keys, use the keys to sign in to their Microsoft accounts on web sites while on FIDO-capable devices, as well as sign in to their Azure AD-joined Windows 10 devices.
112112

113-
For more information, see [Enable passwordless sign in for Azure AD (preview)](https://docs.microsoft.com/azure/active-directory/authentication/howto-authentication-passwordless-enable) for administrator-related information, and [Set up security info to use a security key (Preview)](https://docs.microsoft.com/azure/active-directory/user-help/security-info-setup-security-key) for end-user-related information.
113+
For more information, see [Enable passwordless sign in for Azure AD (preview)](/azure/active-directory/authentication/concept-authentication-passwordless) for administrator-related information, and [Set up security info to use a security key (Preview)](https://docs.microsoft.com/azure/active-directory/user-help/security-info-setup-security-key) for end-user-related information.
114114

115115
---
116116

articles/active-directory/hybrid/how-to-connect-sync-staging-server.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ During installation, you can select the server to be in **staging mode**. This a
3737
3838
You can still force an export by using the synchronization service manager.
3939

40-
A server in staging mode continues to receive changes from Active Directory and Azure AD. It always has a copy of the latest changes and can very fast take over the responsibilities of another server. If you make configuration changes to your primary server, it is your responsibility to make the same changes to the server in staging mode.
40+
A server in staging mode continues to receive changes from Active Directory and Azure AD and can quickly take over the responsibilities of another server in the event of a failure. If you make configuration changes to your primary server, it is your responsibility to make the same changes to the server in staging mode.
4141

4242
For those of you with knowledge of older sync technologies, the staging mode is different since the server has its own SQL database. This architecture allows the staging mode server to be located in a different datacenter.
4343

articles/active-directory/hybrid/reference-connect-sync-functions-reference.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -98,7 +98,7 @@ The BitAnd function sets specified bits on a value.
9898
**Remarks:**
9999
This function converts both parameters to the binary representation and sets a bit to:
100100

101-
* 0 - if one or both of the corresponding bits in *mask* and *flag* are 0
101+
* 0 - if one or both of the corresponding bits in *value1* and *value2* are 0
102102
* 1 - if both of the corresponding bits are 1.
103103

104104
In other words, it returns 0 in all cases except when the corresponding bits of both parameters are 1.
@@ -129,7 +129,7 @@ The CBool function returns a Boolean based on the evaluated expression
129129
`bool CBool(exp Expression)`
130130

131131
**Remarks:**
132-
If the expression evaluates to a nonzero value, then CBool returns True, else it returns False.
132+
If the expression evaluates to a non-zero value, then CBool returns True, else it returns False.
133133

134134
**Example:**
135135
`CBool([attrib1] = [attrib2])`

articles/active-directory/identity-protection/risk-events-reference.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -73,3 +73,8 @@ We also run this detection for basic authentication (or legacy protocols). Becau
7373
**Old name:** This detection will be shown in the legacy Azure AD Identity Protection reports (Users flagged for risk, Risk events) as ‘Users with leaked credentials’
7474

7575
This risk event type indicates user activity that is unusual for the given user or is consistent with known attack patterns based on Microsoft’s internal and external threat intelligence sources.
76+
77+
## Admin confirmed user compromised
78+
79+
**Detection Type:** Offline <br>
80+
This detection indicates an admin has selected ‘Confirm user compromised’ in the Risky users UI or using riskyUsers API. To see which admin has confirmed this user compromised, check the user’s risk history (via UI or API).

articles/active-directory/managed-identities-azure-resources/services-support-managed-identities.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,7 @@ Refer to the following list to configure managed identity for Azure Virtual Mach
5858
| Managed identity type | All Generally Available<br>Global Azure Regions | Azure Government | Azure Germany | Azure China 21Vianet |
5959
| --- | --- | --- | --- | --- |
6060
| System assigned | Available | Available | Available | Available |
61-
| User assigned | Preview | Not available | Not available | Not available |
61+
| User assigned | Available | Not available | Not available | Not available |
6262

6363
Refer to the following list to configure managed identity for Azure App Service (in regions where available):
6464

@@ -84,7 +84,7 @@ Refer to the following list to use a managed identity with [Azure Blueprints](..
8484
Managed identity type |All Generally Available<br>Global Azure Regions | Azure Government | Azure Germany | Azure China 21Vianet |
8585
| --- | --- | --- | --- | --- |
8686
| System assigned | Available | Available | Available | Available |
87-
| User assigned | Preview | Not available | Not available | Not available |
87+
| User assigned | Available | Not available | Not available | Not available |
8888

8989
Refer to the following list to configure managed identity for Azure Functions (in regions where available):
9090

0 commit comments

Comments
 (0)