Skip to content

Commit 3069757

Browse files
committed
Merging changes synced from https://github.com/MicrosoftDocs/azure-docs-pr (branch live)
2 parents d2542cc + aee08b0 commit 3069757

File tree

173 files changed

+1161
-1040
lines changed

Some content is hidden

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

173 files changed

+1161
-1040
lines changed

articles/active-directory/authentication/howto-password-ban-bad-on-premises-operations.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ Follow the guidance in the article [Configuring the custom banned password list]
2525

2626
## Enable Password Protection
2727

28-
1. Sign in to the [Azure portal](https://portal.azure.com) and browse to **Azure Active Directory**, **Authentication methods**, then **Password Protection**.
28+
1. Sign in to the [Azure portal](https://portal.azure.com) and browse to **Azure Active Directory**, **Security**,**Authentication methods**, then **Password Protection**.
2929
1. Set **Enable Password Protection on Windows Server Active Directory** to **Yes**
3030
1. As mentioned in the [Deployment guide](howto-password-ban-bad-on-premises-deploy.md#deployment-strategy), it is recommended to initially set the **Mode** to **Audit**
3131
* After you are comfortable with the feature, you can switch the **Mode** to **Enforced**

articles/active-directory/conditional-access/technical-reference.md

Lines changed: 18 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -27,8 +27,6 @@ This article provides you with support information for the following configurati
2727
- Client applications condition
2828
- Approved client application requirement
2929

30-
If this is not the information you are looking for, please leave a comment at the end of this article.
31-
3230
## Cloud apps assignments
3331

3432
With Conditional Access policies, you control how your users access your [cloud apps](conditions.md#cloud-apps-and-actions). When you configure a Conditional Access policy, you need to select at least one cloud app.
@@ -39,6 +37,7 @@ With Conditional Access policies, you control how your users access your [cloud
3937

4038
You can assign a Conditional Access policy to the following cloud apps from Microsoft:
4139

40+
- Office 365 (preview)
4241
- Azure Analysis Services
4342
- Azure DevOps
4443
- Azure SQL Database and Data Warehouse - [Learn more](https://docs.microsoft.com/azure/sql-database/sql-database-conditional-access)
@@ -72,6 +71,22 @@ You can assign a Conditional Access policy to the following cloud apps from Micr
7271
- Virtual Private Network (VPN)
7372
- Windows Defender ATP
7473

74+
### Office 365 (preview)
75+
76+
Office 365 provides cloud-based productivity and collaboration services like Exchange, SharePoint, and Microsoft Teams. Office 365 cloud services are deeply integrated to ensure smooth and collaborative experiences. The Office 365 (preview) app makes it possible to target these services all at once. We recommend using the new Office 365 (preview) app, instead of targeting individual cloud apps like Office 365 Exchange Online and Office 365 SharePoint Online to avoid issues that may arise due to inconsistent policies and service dependencies.
77+
78+
Key applications that are included in the Office 365 (preview) client app:
79+
80+
- Office 365 Exchange Online
81+
- Office 365 SharePoint Online
82+
- Microsoft Teams
83+
- Office 365 Yammer
84+
- Office portal
85+
- Microsoft Forms
86+
- Microsoft Power Automate
87+
- Microsoft Planner
88+
- Microsoft PowerApps
89+
7590
### Other applications
7691

7792
In addition to the Microsoft cloud apps, you can assign a Conditional Access policy to the following types of cloud apps:
@@ -169,7 +184,7 @@ This setting has an impact on access attempts made from the following mobile app
169184
| Dynamics CRM app | Dynamics CRM | Windows 10, Windows 8.1, iOS, and Android |
170185
| Mail/Calendar/People app, Outlook 2016, Outlook 2013 (with modern authentication)| Office 365 Exchange Online | Windows 10 |
171186
| MFA and location policy for apps. Device based policies are not supported.| Any My Apps app service| Android and iOS |
172-
| Microsoft Teams Services - this controls all services that support Microsoft Teams and all its Client Apps - Windows Desktop, iOS, Android, WP, and web client | Microsoft Teams | Windows 10, Windows 8.1, Windows 7, iOS, Android and macOS |
187+
| Microsoft Teams Services - this controls all services that support Microsoft Teams and all its Client Apps - Windows Desktop, iOS, Android, WP, and web client | Microsoft Teams | Windows 10, Windows 8.1, Windows 7, iOS, Android, and macOS |
173188
| Office 2016 apps, Office 2013 (with modern authentication), OneDrive sync client (see [notes](https://support.office.com/en-US/article/Azure-Active-Directory-conditional-access-with-the-OneDrive-sync-client-on-Windows-028d73d7-4b86-4ee0-8fb7-9a209434b04e)) | Office 365 SharePoint Online | Windows 8.1, Windows 7 |
174189
| Office 2016 apps, Universal Office apps, Office 2013 (with modern authentication), OneDrive sync client (see [notes](https://support.office.com/en-US/article/Azure-Active-Directory-conditional-access-with-the-OneDrive-sync-client-on-Windows-028d73d7-4b86-4ee0-8fb7-9a209434b04e)), Office Groups support is planned for the future, SharePoint app support is planned for the future | Office 365 SharePoint Online | Windows 10 |
175190
| Office 2016 (Word, Excel, PowerPoint, OneNote only). OneDrive for Business support planned for the future| Office 365 SharePoint Online| macOS|

articles/active-directory/devices/hybrid-azuread-join-control.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@ Use the following example to create a Group Policy Object (GPO) to deploy a regi
7676

7777
### Configure AD FS settings
7878

79-
If you are using AD FS, you first need to configure client-side SCP using the instructions mentioned above but linking the GPO to your AD FS servers. The SCP object defines the source of authority for device objects. It can be on-premises or Azure AD. When this is configured for AD FS, the source for device objects is established as Azure AD.
79+
If you are using AD FS, you first need to configure client-side SCP using the instructions mentioned above by linking the GPO to your AD FS servers. The SCP object defines the source of authority for device objects. It can be on-premises or Azure AD. When client-side SCP is configured for AD FS, the source for device objects is established as Azure AD.
8080

8181
> [!NOTE]
8282
> If you failed to configure client-side SCP on your AD FS servers, the source for device identities would be considered as on-premises. ADFS will then start deleting device objects from on-premises directory after the stipulated period defined in the ADFS Device Registration's attribute "MaximumInactiveDays". ADFS Device Registration objects can be found using the [Get-AdfsDeviceRegistration cmdlet](https://docs.microsoft.com/powershell/module/adfs/get-adfsdeviceregistration?view=win10-ps).

articles/active-directory/fundamentals/active-directory-manage-groups.md

Lines changed: 10 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -9,25 +9,32 @@ ms.service: active-directory
99
ms.workload: identity
1010
ms.subservice: fundamentals
1111
ms.topic: conceptual
12-
ms.date: 08/28/2017
12+
ms.date: 01/08/2020
1313
ms.author: ajburnle
1414
ms.reviewer: piotrci
1515
ms.custom: "it-pro, seodec18"
1616
ms.collection: M365-identity-device-management
1717
---
1818

1919
# Manage app and resource access using Azure Active Directory groups
20-
Azure Active Directory (Azure AD) helps you to manage your cloud-based apps, on-premises apps, and your resources using your organization's groups. Your resources can be part of the directory, such as permissions to manage objects through roles in the directory, or external to the directory, such as for Software as a Service (SaaS) apps, Azure services, SharePoint sites, and on-premises resources.
20+
Azure Active Directory (Azure AD) lets you use groups to manage access to your cloud-based apps, on-premises apps, and your resources. Your resources can be part of the Azure AD organization, such as permissions to manage objects through roles in Azure AD, or external to the organization, such as for Software as a Service (SaaS) apps, Azure services, SharePoint sites, and on-premises resources.
2121

2222
>[!NOTE]
2323
>To use Azure Active Directory, you need an Azure account. If you don't have an account, you can [sign up for a free Azure account](https://azure.microsoft.com/free/).
24+
>
25+
> In the Azure portal, you can see some groups whose membership and group details you can't manage in the portal:
26+
>
27+
> - Groups synced from on-premises Active Directory can be managed only in on-premises Active Directory.
28+
> - Other group types such as distribution lists and mail-enabled security groups are managed only in Exchange admin center or Microsoft 365 admin center. You must sign in to Exchange admin center or Microsoft 365 admin center to manage these groups.
29+
30+
## How access management in Azure AD works
2431

25-
## How does access management in Azure AD work?
2632
Azure AD helps you give access to your organization's resources by providing access rights to a single user or to an entire Azure AD group. Using groups lets the resource owner (or Azure AD directory owner), assign a set of access permissions to all the members of the group, instead of having to provide the rights one-by-one. The resource or directory owner can also give management rights for the member list to someone else, such as a department manager or a Helpdesk administrator, letting that person add and remove members, as needed. For more information about how to manage group owners, see [Manage group owners](active-directory-accessmanagement-managing-group-owners.md)
2733

2834
![Azure Active Directory access management diagram](./media/active-directory-manage-groups/active-directory-access-management-works.png)
2935

3036
## Ways to assign access rights
37+
3138
There are four ways to assign resource access rights to your users:
3239

3340
- **Direct assignment.** The resource owner directly assigns the user to the resource.

articles/active-directory/hybrid/whatis-azure-ad-connect.md

Lines changed: 3 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: overview
10-
ms.date: 02/26/2019
10+
ms.date: 01/08/2020
1111
ms.subservice: hybrid
1212
ms.author: billmath
1313
ms.topic: conceptual
@@ -64,8 +64,8 @@ Rich [usage metrics](how-to-connect-health-adfs.md#usage-analytics-for-ad-fs)|To
6464

6565
[!INCLUDE [active-directory-free-license.md](../../../includes/active-directory-free-license.md)]
6666

67-
68-
67+
## License requirements for using Azure AD Connect Health
68+
[!INCLUDE [active-directory-free-license.md](../../../includes/active-directory-p1-license.md)]
6969

7070
## Next steps
7171

0 commit comments

Comments
 (0)