Skip to content

Commit 86453ed

Browse files
committed
Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into tamram-0519
2 parents ec79dc3 + d51b81d commit 86453ed

File tree

55 files changed

+1232
-102
lines changed

Some content is hidden

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

55 files changed

+1232
-102
lines changed

.vscode/settings.json

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,8 @@
5959
"YAML"
6060
],
6161
"cSpell.words": [
62-
"auditd"
62+
"auditd",
63+
"covid"
6364
],
6465
"git.ignoreLimitWarning": true
6566
}

articles/active-directory/app-provisioning/customize-application-attributes.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -102,7 +102,7 @@ Applications and systems that support customization of the attribute list includ
102102
- Salesforce
103103
- ServiceNow
104104
- Workday
105-
- Azure Active Directory ([Microsoft Graph REST API v1.0 reference](https://docs.microsoft.com/graph/api/overview?view=graph-rest-1.0) and custom directory extensions are supported)
105+
- Azure Active Directory ([Azure AD Graph API default attributes](https://msdn.microsoft.com/Library/Azure/Ad/Graph/api/entity-and-complex-type-reference#user-entity) and custom directory extensions are supported)
106106
- Apps that support [SCIM 2.0](https://tools.ietf.org/html/rfc7643), where attributes defined in the [core schema](https://tools.ietf.org/html/rfc7643) need to be added
107107

108108
> [!NOTE]

articles/active-directory/conditional-access/howto-conditional-access-insights-reporting.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -33,9 +33,6 @@ The following roles can access insights and reporting:
3333

3434
Users also need one of the following Log Analytics workspace roles:
3535

36-
- Reader
37-
- Monitoring reader
38-
- Log Analytics reader
3936
- Contributor
4037
- Owner
4138

articles/active-directory/hybrid/reference-connect-version-history.md

Lines changed: 6 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -8,12 +8,11 @@ ms.assetid: ef2797d7-d440-4a9a-a648-db32ad137494
88
ms.service: active-directory
99
ms.topic: reference
1010
ms.workload: identity
11-
ms.date: 04/23/2020
11+
ms.date: 05/07/2020
1212
ms.subservice: hybrid
1313
ms.author: billmath
1414

1515
ms.collection: M365-identity-device-management
16-
ms.custom: has-adal-ref
1716
---
1817
# Azure AD Connect: Version release history
1918
The Azure Active Directory (Azure AD) team regularly updates Azure AD Connect with new features and functionality. Not all additions are applicable to all audiences.
@@ -50,10 +49,7 @@ Not all releases of Azure AD Connect will be made available for auto upgrade. Th
5049
05/07/2020: Released for download
5150

5251
### Fixed issues
53-
- Fixed an issue where unselected domains were getting incorrectly selected from the wizard UI.
54-
- Fixed an issue in the ADSyncConfig PowerShell module, where invoking DSACLS command used in all the Set-ADSync* Permissions cmdlets would cause one of the following errors:
55-
- `GrantAclsNoInheritance : The parameter is incorrect. The command failed to complete successfully.`
56-
- `GrantAcls : No GUID Found for computer …`
52+
This hotfix build fixes an issue where unselected domains were getting incorrectly selected from the wizard UI if only grandchild containers were selected.
5753

5854
## 1.5.29.0
5955

@@ -77,7 +73,10 @@ This hotfix build fixes an issue in build 1.5.20.0 if you have cloned the **In f
7773
04/09/2020: Released for download
7874

7975
### Fixed issues
80-
This hotfix build fixes an issue with build 1.5.18.0 if you have the Group Filtering feature enabled and use mS-DS-ConsistencyGuid as the source anchor.
76+
- This hotfix build fixes an issue with build 1.5.18.0 if you have the Group Filtering feature enabled and use mS-DS-ConsistencyGuid as the source anchor.
77+
- Fixed an issue in the ADSyncConfig PowerShell module, where invoking DSACLS command used in all the Set-ADSync* Permissions cmdlets would cause one of the following errors:
78+
- `GrantAclsNoInheritance : The parameter is incorrect. The command failed to complete successfully.`
79+
- `GrantAcls : No GUID Found for computer …`
8180

8281
> [!IMPORTANT]
8382
> If you have cloned the **In from AD - Group Join** sync rule and have not cloned the **In from AD - Group Common** sync rule and plan to upgrade, complete the following steps as part of the upgrade:
@@ -112,7 +111,6 @@ This hotfix build fixes an issue with build 1.5.18.0 if you have the Group Filte
112111
- Fixed an issue with the creation of the Azure Active Directory synchronization account where enabling Directory Extensions or PHS may fail because the account has not propagated across all service replicas before attempted use.
113112
- Fixed a bug in the sync errors compression utility that was not handling surrogate characters correctly.
114113
- Fixed a bug in the auto upgrade which left the server in the scheduler suspended state.
115-
- Fixed a bug in the Domain/OU filtering page that would remove the Run Profiles of a domain by just partially expanding the domain tree, without making any changes.
116114

117115
## 1.4.38.0
118116
### Release status

articles/active-directory/identity-protection/overview-identity-protection.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -83,6 +83,8 @@ Identity Protection requires users be a Security Reader, Security Operator, Secu
8383
| Security operator | View all Identity Protection reports and Overview blade <br><br> Dismiss user risk, confirm safe sign-in, confirm compromise | Configure or change policies <br><br> Reset password for a user <br><br> Configure alerts |
8484
| Security reader | View all Identity Protection reports and Overview blade | Configure or change policies <br><br> Reset password for a user <br><br> Configure alerts <br><br> Give feedback on detections |
8585

86+
Currently, the security operator role cannot access the Risky sign-ins report.
87+
8688
Conditional Access administrators can also create policies that factor in sign-in risk as a condition, find more information in the article [Conditional Access: Conditions](../conditional-access/concept-conditional-access-conditions.md#sign-in-risk).
8789

8890
## License requirements
Lines changed: 172 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,172 @@
1+
---
2+
title: 'Tutorial: Azure Active Directory single sign-on (SSO) integration with ColorTokens ZTNA | Microsoft Docs'
3+
description: Learn how to configure single sign-on between Azure Active Directory and ColorTokens ZTNA.
4+
services: active-directory
5+
documentationCenter: na
6+
author: jeevansd
7+
manager: mtillman
8+
ms.reviewer: barbkess
9+
10+
ms.assetid: 2e6423a8-6ee4-4a67-8ac8-2061292faf40
11+
ms.service: active-directory
12+
ms.subservice: saas-app-tutorial
13+
ms.workload: identity
14+
ms.tgt_pltfrm: na
15+
ms.topic: tutorial
16+
ms.date: 05/15/2020
17+
ms.author: jeedes
18+
19+
ms.collection: M365-identity-device-management
20+
---
21+
22+
# Tutorial: Azure Active Directory single sign-on (SSO) integration with ColorTokens ZTNA
23+
24+
In this tutorial, you'll learn how to integrate ColorTokens ZTNA with Azure Active Directory (Azure AD). When you integrate ColorTokens ZTNA with Azure AD, you can:
25+
26+
* Control in Azure AD who has access to ColorTokens ZTNA.
27+
* Enable your users to be automatically signed-in to ColorTokens ZTNA with their Azure AD accounts.
28+
* Manage your accounts in one central location - the Azure portal.
29+
30+
To learn more about SaaS app integration with Azure AD, see [What is application access and single sign-on with Azure Active Directory](https://docs.microsoft.com/azure/active-directory/manage-apps/what-is-single-sign-on).
31+
32+
## Prerequisites
33+
34+
To get started, you need the following items:
35+
36+
* An Azure AD subscription. If you don't have a subscription, you can get a [free account](https://azure.microsoft.com/free/).
37+
* ColorTokens ZTNA single sign-on (SSO) enabled subscription.
38+
39+
## Scenario description
40+
41+
In this tutorial, you configure and test Azure AD SSO in a test environment.
42+
43+
* ColorTokens ZTNA supports **SP** initiated SSO
44+
* Once you configure ColorTokens ZTNA you can enforce session control, which protect exfiltration and infiltration of your organization’s sensitive data in real-time. Session control extend from Conditional Access. [Learn how to enforce session control with Microsoft Cloud App Security](https://docs.microsoft.com/cloud-app-security/proxy-deployment-any-app).
45+
46+
## Adding ColorTokens ZTNA from the gallery
47+
48+
To configure the integration of ColorTokens ZTNA into Azure AD, you need to add ColorTokens ZTNA from the gallery to your list of managed SaaS apps.
49+
50+
1. Sign in to the [Azure portal](https://portal.azure.com) using either a work or school account, or a personal Microsoft account.
51+
1. On the left navigation pane, select the **Azure Active Directory** service.
52+
1. Navigate to **Enterprise Applications** and then select **All Applications**.
53+
1. To add new application, select **New application**.
54+
1. In the **Add from the gallery** section, type **ColorTokens ZTNA** in the search box.
55+
1. Select **ColorTokens ZTNA** from results panel and then add the app. Wait a few seconds while the app is added to your tenant.
56+
57+
## Configure and test Azure AD single sign-on for ColorTokens ZTNA
58+
59+
Configure and test Azure AD SSO with ColorTokens ZTNA using a test user called **B.Simon**. For SSO to work, you need to establish a link relationship between an Azure AD user and the related user in ColorTokens ZTNA.
60+
61+
To configure and test Azure AD SSO with ColorTokens ZTNA, complete the following building blocks:
62+
63+
1. **[Configure Azure AD SSO](#configure-azure-ad-sso)** - to enable your users to use this feature.
64+
1. **[Create an Azure AD test user](#create-an-azure-ad-test-user)** - to test Azure AD single sign-on with B.Simon.
65+
1. **[Assign the Azure AD test user](#assign-the-azure-ad-test-user)** - to enable B.Simon to use Azure AD single sign-on.
66+
1. **[Configure ColorTokens ZTNA SSO](#configure-colortokens-ztna-sso)** - to configure the single sign-on settings on application side.
67+
1. **[Create ColorTokens ZTNA test user](#create-colortokens-ztna-test-user)** - to have a counterpart of B.Simon in ColorTokens ZTNA that is linked to the Azure AD representation of user.
68+
1. **[Test SSO](#test-sso)** - to verify whether the configuration works.
69+
70+
## Configure Azure AD SSO
71+
72+
Follow these steps to enable Azure AD SSO in the Azure portal.
73+
74+
1. In the [Azure portal](https://portal.azure.com/), on the **ColorTokens ZTNA** application integration page, find the **Manage** section and select **single sign-on**.
75+
1. On the **Select a single sign-on method** page, select **SAML**.
76+
1. On the **Set up single sign-on with SAML** page, click the edit/pen icon for **Basic SAML Configuration** to edit the settings.
77+
78+
![Edit Basic SAML Configuration](common/edit-urls.png)
79+
80+
1. On the **Basic SAML Configuration** section, enter the values for the following fields:
81+
82+
a. In the **Sign on URL** text box, type a URL using the following pattern:
83+
`https://<COLORMASTER_HOST>/colormaster/api/v1/<TENANT_NAME>/saml/login?resourceId=<RESOURCEID>&iwa=<TRUE/FALSE>`
84+
85+
b. In the **Identifier (Entity ID)** text box, type a URL using the following pattern:
86+
`https://<COLORMASTER_HOST>.com/<TENANT_NAME>`
87+
88+
c. In the **Reply URL** text box, type a URL using the following pattern:
89+
`https://<COLORMASTER_HOST>.com/<TENANT_NAME>`
90+
91+
> [!NOTE]
92+
> These values are not real. Update these values with the actual Sign on URL, Identifier and Reply URL. Contact [ColorTokens ZTNA Client support team](mailto:[email protected]) to get these values. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
93+
94+
1. ColorTokens ZTNA application expects the SAML assertions in a specific format, which requires you to add custom attribute mappings to your SAML token attributes configuration. The following screenshot shows the list of default attributes.
95+
96+
![image](common/default-attributes.png)
97+
98+
1. In addition to above, ColorTokens ZTNA application expects few more attributes to be passed back in SAML response which are shown below. These attributes are also pre populated but you can review them as per your requirements.
99+
100+
| Name | Source Attribute|
101+
| ------------- | --------- |
102+
| department | user.userprincipalname |
103+
| Group | user.groups |
104+
105+
> [!NOTE]
106+
> Click [here](https://docs.microsoft.com/azure/active-directory/develop/active-directory-enterprise-app-role-management) to know how to create roles in Azure AD.
107+
108+
1. On the **Set up single sign-on with SAML** page, in the **SAML Signing Certificate** section, find **Federation Metadata XML** and select **Download** to download the certificate and save it on your computer.
109+
110+
![The Certificate download link](common/metadataxml.png)
111+
112+
1. On the **Set up ColorTokens ZTNA** section, copy the appropriate URL(s) based on your requirement.
113+
114+
![Copy configuration URLs](common/copy-configuration-urls.png)
115+
116+
### Create an Azure AD test user
117+
118+
In this section, you'll create a test user in the Azure portal called B.Simon.
119+
120+
1. From the left pane in the Azure portal, select **Azure Active Directory**, select **Users**, and then select **All users**.
121+
1. Select **New user** at the top of the screen.
122+
1. In the **User** properties, follow these steps:
123+
1. In the **Name** field, enter `B.Simon`.
124+
1. In the **User name** field, enter the [email protected]. For example, `[email protected]`.
125+
1. Select the **Show password** check box, and then write down the value that's displayed in the **Password** box.
126+
1. Click **Create**.
127+
128+
### Assign the Azure AD test user
129+
130+
In this section, you'll enable B.Simon to use Azure single sign-on by granting access to ColorTokens ZTNA.
131+
132+
1. In the Azure portal, select **Enterprise Applications**, and then select **All applications**.
133+
1. In the applications list, select **ColorTokens ZTNA**.
134+
1. In the app's overview page, find the **Manage** section and select **Users and groups**.
135+
136+
![The "Users and groups" link](common/users-groups-blade.png)
137+
138+
1. Select **Add user**, then select **Users and groups** in the **Add Assignment** dialog.
139+
140+
![The Add User link](common/add-assign-user.png)
141+
142+
1. In the **Users and groups** dialog, select **B.Simon** from the Users list, then click the **Select** button at the bottom of the screen.
143+
1. If you're expecting any role value in the SAML assertion, in the **Select Role** dialog, select the appropriate role for the user from the list and then click the **Select** button at the bottom of the screen.
144+
1. In the **Add Assignment** dialog, click the **Assign** button.
145+
146+
## Configure ColorTokens ZTNA SSO
147+
148+
To configure single sign-on on **ColorTokens ZTNA** side, you need to send the downloaded **Federation Metadata XML** and appropriate copied URLs from Azure portal to [ColorTokens ZTNA support team](mailto:[email protected]). They set this setting to have the SAML SSO connection set properly on both sides.
149+
150+
### Create ColorTokens ZTNA test user
151+
152+
In this section, you create a user called Britta Simon in ColorTokens ZTNA. Work with [ColorTokens ZTNA support team](mailto:[email protected]) to add the users in the ColorTokens ZTNA platform. Users must be created and activated before you use single sign-on.
153+
154+
## Test SSO
155+
156+
In this section, you test your Azure AD single sign-on configuration using the Access Panel.
157+
158+
When you click the ColorTokens ZTNA tile in the Access Panel, you should be automatically signed in to the ColorTokens ZTNA for which you set up SSO. For more information about the Access Panel, see [Introduction to the Access Panel](https://docs.microsoft.com/azure/active-directory/active-directory-saas-access-panel-introduction).
159+
160+
## Additional resources
161+
162+
- [ List of Tutorials on How to Integrate SaaS Apps with Azure Active Directory ](https://docs.microsoft.com/azure/active-directory/active-directory-saas-tutorial-list)
163+
164+
- [What is application access and single sign-on with Azure Active Directory? ](https://docs.microsoft.com/azure/active-directory/active-directory-appssoaccess-whatis)
165+
166+
- [What is conditional access in Azure Active Directory?](https://docs.microsoft.com/azure/active-directory/conditional-access/overview)
167+
168+
- [Try ColorTokens ZTNA with Azure AD](https://aad.portal.azure.com/)
169+
170+
- [What is session control in Microsoft Cloud App Security?](https://docs.microsoft.com/cloud-app-security/proxy-intro-aad)
171+
172+
- [How to protect ColorTokens ZTNA with advanced visibility and controls](https://docs.microsoft.com/cloud-app-security/proxy-intro-aad)

0 commit comments

Comments
 (0)