Skip to content

Commit 63e4ffb

Browse files
authored
Merge pull request #6532 from MicrosoftDocs/FromPrivateRepo
From private repo
2 parents 9de2375 + a4265a4 commit 63e4ffb

File tree

267 files changed

+2883
-1677
lines changed

Some content is hidden

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

267 files changed

+2883
-1677
lines changed

.openpublishing.redirection.json

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17777,7 +17777,11 @@
1777717777
"source_path": "articles/monitoring/management-overview-monitoring.md",
1777817778
"redirect_url": "/azure/monitoring/",
1777917779
"redirect_document_id": false
17780+
},
17781+
{
17782+
"source_path": "articles/cli-install-nodejs.md",
17783+
"redirect_url": "/cli/azure/install-cli-version-1.0",
17784+
"redirect_document_id": false
1778017785
}
17781-
1778217786
]
1778317787
}

articles/active-directory/active-directory-conditional-access-controls.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.devlang: na
1414
ms.topic: article
1515
ms.tgt_pltfrm: na
1616
ms.workload: identity
17-
ms.date: 02/09/2018
17+
ms.date: 03/28/2018
1818
ms.author: markvi
1919
ms.reviewer: calebb
2020

@@ -73,11 +73,15 @@ Using multi-factor authentication helps protect resources from being accessed by
7373

7474
### Compliant device
7575

76-
You can configure conditional access policies that are device-based. The objective of a device-based conditional access policy is to grant access to the configured resources only from trusted devices. Requiring a compliant device is one option you have to define what a trusted device is. For more information, see [set up Azure Active Directory device-based conditional access policies](active-directory-conditional-access-policy-connected-applications.md).
76+
You can configure conditional access policies that are device-based. The objective of a device-based conditional access policy is to grant access to the configured resources only from trusted devices. Requiring a compliant device is one option you have to define what a trusted device is. If this option is selected, your conditional access policy grants access to access attempts made with devices that are joined to your Azure Active Directory and are marked as compliant by your MDM solution.
77+
78+
For more information, see [set up Azure Active Directory device-based conditional access policies](active-directory-conditional-access-policy-connected-applications.md).
7779

7880
### Domain-joined device
7981

80-
Requiring a domain-joined device is another option you have to configure device-based conditional access policies. This requirement refers to Windows desktops, laptops, and enterprise tablets that are joined to an on-premises Active Directory. For more information, see [set up Azure Active Directory device-based conditional access policies](active-directory-conditional-access-policy-connected-applications.md).
82+
Requiring a domain-joined device is another option you have to configure device-based conditional access policies. This requirement refers to Windows desktops, laptops, and enterprise tablets that are joined to an on-premises Active Directory. If this option is selected, your conditional access policy grants access to access attempts made with devices that are joined to your on-premises Active Directory and your Azure Active Directory.
83+
84+
For more information, see [set up Azure Active Directory device-based conditional access policies](active-directory-conditional-access-policy-connected-applications.md).
8185

8286

8387

articles/active-directory/active-directory-tou.md

Lines changed: 36 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,7 @@
11
---
22
title: 'Azure Active Directory Terms of Use| Microsoft Docs'
3-
description: Azure AD Terms of Use will allow you and your company the ability to provide terms of use to users of Azure AD servcies.
3+
description: Azure AD Terms of Use will allow you and your company the ability to provide terms of use to users of Azure AD services.
44
services: active-directory
5-
documentationcenter: ''
65
author: billmath
76
manager: mtillman
87
editor: ''
@@ -12,20 +11,20 @@ ms.workload: identity
1211
ms.tgt_pltfrm: na
1312
ms.devlang: na
1413
ms.topic: get-started-article
15-
ms.date: 03/06/2018
14+
ms.date: 03/29/2018
1615
ms.author: billmath
1716

1817
---
1918

20-
# Azure Active Directory Terms of Use feature (Preview)
21-
Azure AD Terms of Use provides a simple method organizations can use to present information to end users. This ensures users see relevant disclaimers for legal or compliance requirements.
19+
# Azure Active Directory Terms of Use feature
20+
Azure AD Terms of Use provides a simple method organizations can use to present information to end users. This presentation, ensures users see relevant disclaimers for legal or compliance requirements.
2221

23-
Azure AD Terms of Use uses the pdf format to present content. This pdf can be any content, such as existing contract documents, allowing you to collect end user agreements during user sign-in. You can use the terms of use for applications, groups of users, or if you have multiple terms of use for different purposes.
22+
Azure AD Terms of Use uses the pdf format to present content. The pdf can be any content, such as existing contract documents, allowing you to collect end user agreements during user sign-in. You can use the terms of use for applications, groups of users, or if you have multiple terms of use for different purposes.
2423

2524
The remainder of this document describes how to get going with Azure AD Terms of Use.
2625

2726
## Why use Azure AD Terms of Use
28-
Finding it difficult to get employee’s or guests to agree to your terms of use before getting access? Need help figuring out who has or hasn’t agreed to your company terms of use? Azure AD Terms of Use provides a simple method organizations can use to present information to end users. This ensures that they see relevant disclaimers for legal or compliance requirements.
27+
Finding it difficult to get employee’s or guests to agree to your terms of use before getting access? Need help figuring out who has or hasn’t agreed to your company terms of use? Azure AD Terms of Use provides a simple method organizations can use to present information to end users. This presentation, ensures that they see relevant disclaimers for legal or compliance requirements.
2928

3029
Azure AD Terms of Use can be used in the following scenarios:
3130
- General terms of use for all users in your organization.
@@ -51,11 +50,11 @@ Once you have finalized your Terms of Use, use the following procedure to add it
5150
2. Click Add.</br>
5251
![Add TOU](media/active-directory-tou/tou12.png)
5352
3. Enter the **Name** for the Terms of Use
54-
4. Enter **Display Name**. This header is what users see when they sign in.
53+
4. Enter **Display Name**. The header is what users see when they sign in.
5554
5. **Browse** to your finalized terms of use pdf and select it. The recommended font size is 24.
5655
6. **Select** a language for the terms of use. The language option allows you to upload multiple terms of use, each with a different language. The version of the terms of use that an end user will see will be based on their browser preferences.
5756
7. Select either on or off for **Require users to expand the terms of use**. If this is set to on, end users will be required to view the terms of use prior to accepting them.
58-
8. Under the **Conditional Access** section you can **Enforce** the uploaded terms of use by using a template or a custom conditional access policy. Custom conditional access policies enables granular terms of use, down to a specific cloud application or group of users. For more information, see [configuring conditional access policies](active-directory-conditional-access-best-practices.md)
57+
8. Under the **Conditional Access**, you can **Enforce** the uploaded terms of use by selecting a template from the drop-down or a custom conditional access policy. Custom conditional access policies enables granular terms of use, down to a specific cloud application or group of users. For more information, see [configuring conditional access policies](active-directory-conditional-access-best-practices.md)
5958
9. Click **Create**.
6059
10. If you selected a custom conditional access template, then a new screen appears which allows you to customize the CA policy.
6160
11. You should now see your new Terms of Use.</br>
@@ -72,17 +71,33 @@ You can remove or delete old terms of use using the following procedure:
7271
4. You should no longer see your new terms of use.
7372

7473

74+
## Viewing current user status
75+
You will notice that your terms of use shows a count for users who have accepted and declined.
76+
77+
![Audit Event](media/active-directory-tou/tou15.png)
78+
79+
You can click on the numbers under **accepted** or **declined** to view the current state of users.
80+
81+
![Audit Event](media/active-directory-tou/tou16.png)
82+
7583
## Audit Terms of Use
76-
Azure AD Terms of Use provides easy to use auditing so that you can see who has accepted and when they accepted your terms of use. To get started with auditing use the following procedure:
84+
If you want to view historical acceptances and declines and not just the current status, Azure AD Terms of Use provides easy to use auditing. This auditing allows you to see who has accepted and when they accepted your terms of use.
85+
86+
There are two ways in which you can use auditing depending on what you are currently trying to do.
87+
88+
89+
To get started with auditing use the following procedure:
7790

7891
### To audit Terms of Use
7992
1. Navigate to the dashboard at [https://aka.ms/catou](https://aka.ms/catou)
80-
2. Click Audit Event.</br>
93+
2. Click View audit logs.</br>
8194
![Audit Event](media/active-directory-tou/tou8.png)
8295
3. On the Azure AD audit logs screen, you can filter the information using the provided drops downs to target specific audit log information.
8396
![Audit Event](media/active-directory-tou/tou9.png)
8497
4. You can also download the information in a .csv file for use locally.
8598

99+
##
100+
86101
## What users see
87102
Users, who are in scope, will see the following once a terms of use is created and enforced. They will see these screens during sign in.
88103
- Best practice is to have the font within the PDF at size 24.
@@ -91,7 +106,7 @@ Users, who are in scope, will see the following once a terms of use is created a
91106
![Audit Event](media/active-directory-tou/tou11.png)
92107

93108
### Review terms of use
94-
Users can review and see the terms of use that they have accepted. This can be done using the following procedure:
109+
Users can review and see the terms of use that they have accepted. To review terms of use, use the following procedure:
95110

96111
1. Navigate and sign-in to [https://myapps.microsoft.com](https://myapps.microsoft.com).
97112
2. In upper right corner, click your name and select **Profile** from the drop-down.
@@ -100,17 +115,18 @@ Users can review and see the terms of use that they have accepted. This can be
100115
3. On your Profile, click **Review terms of use**.
101116
![Audit Event](media/active-directory-tou/tou13a.png)
102117

103-
4. From there you can review the terms of use you have accepted.
118+
4. From there, you can review the terms of use you have accepted.
104119

105120

106121
## Additional information
107122
The following information is something to be aware of and can assist with using terms of use.
108123

109-
Users in scope will need to sign-out and sign-in in order to satisfy a new policy if:
110-
- a conditional access policy is enabled on a terms of use
111-
- or a second terms of use is created
112-
113-
This is because conditional access policies take effect immediately. When this happens the admin will start to see “sad clouds” or "Azure AD token issues". The admin must sign-out and sign-in again in order to satisfy the new policy.
124+
>[!IMPORTANT]
125+
> Users in scope will need to sign-out and sign-in in order to satisfy a new policy if:
126+
> - a conditional access policy is enabled on a terms of use
127+
> - or a second terms of use is created
128+
>
129+
>Conditional access policies take effect immediately. When this happens the admin will start to see “sad clouds” or "Azure AD token issues". The admin must sign-out and sign-in again in order to satisfy the new policy.
114130
115131

116132

@@ -119,10 +135,10 @@ This is because conditional access policies take effect immediately. When this h
119135
## Frequently asked questions
120136

121137
**Q: How do I see when/if a user has accepted a terms of use?**</br>
122-
A: A user accepting the terms of use is written to the audit log. You can search the Azure AD audit log to see the results.
138+
A: You can simply click on the number under accepted next to your terms of use. For more information, see [Viewing current user status](#viewing-current-user-status). Also, a user accepting the terms of use is written to the audit log. You can search the Azure AD audit log to see the results.
123139

124140
**Q: If you change the terms of use terms does it require users to accept again?**</br>
125-
A: Yes, an administrator can change the terms of use terms and it requires re-accepting the new terms.
141+
A: Yes, an administrator can change the terms of use terms and it requires reaccepting the new terms.
126142

127143
**Q: Can a terms of use support multiple languages?**</br>
128144
A: Yes. Currently there are 18 different languages an administrator can configure for a single terms of use.
-31.2 KB
Loading
-96.6 KB
Loading
34.1 KB
Loading
30.2 KB
Loading
-21.1 KB
Loading
-21.2 KB
Loading

0 commit comments

Comments
 (0)