Skip to content

Commit 6cf9e8f

Browse files
committed
Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into release-build-synapse-sqldw
2 parents 25bc1f1 + 90a6180 commit 6cf9e8f

File tree

420 files changed

+6931
-2351
lines changed

Some content is hidden

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

420 files changed

+6931
-2351
lines changed

.openpublishing.redirection.json

Lines changed: 26 additions & 531 deletions
Large diffs are not rendered by default.

articles/active-directory-domain-services/faqs.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -87,6 +87,7 @@ Yes. Each Azure AD Domain Services managed domain includes two domain controller
8787
* [Can I modify or add DNS records in my managed domain?](#can-i-modify-or-add-dns-records-in-my-managed-domain)
8888
* [What is the password lifetime policy on a managed domain?](#what-is-the-password-lifetime-policy-on-a-managed-domain)
8989
* [Does Azure AD Domain Services provide AD account lockout protection?](#does-azure-ad-domain-services-provide-ad-account-lockout-protection)
90+
* [Can I configure Distributed File System (DFS) and replication within Azure AD Domain Services?](#can-i-configure-distributed-file-system-and-replication-within-azure-ad-domain-services)
9091

9192
### Can I connect to the domain controller for my managed domain using Remote Desktop?
9293
No. You don't have permissions to connect to domain controllers for the managed domain using Remote Desktop. Members of the *AAD DC Administrators* group can administer the managed domain using AD administration tools such as the Active Directory Administration Center (ADAC) or AD PowerShell. These tools are installed using the *Remote Server Administration Tools* feature on a Windows server joined to the managed domain. For more information, see [Create a management VM to configure and administer an Azure AD Domain Services managed domain](tutorial-create-management-vm.md).
@@ -115,6 +116,9 @@ The default password lifetime on an Azure AD Domain Services managed domain is 9
115116
### Does Azure AD Domain Services provide AD account lockout protection?
116117
Yes. Five invalid password attempts within 2 minutes on the managed domain cause a user account to be locked out for 30 minutes. After 30 minutes, the user account is automatically unlocked. Invalid password attempts on the managed domain don't lock out the user account in Azure AD. The user account is locked out only within your Azure AD Domain Services managed domain. For more information, see [Password and account lockout policies on managed domains](password-policy.md).
117118

119+
### Can I configure Distributed File System and replication within Azure AD Domain Services?
120+
No. Distributed File System (DFS) and replication aren't available when using Azure AD Domain Services.
121+
118122
## Billing and availability
119123

120124
* [Is Azure AD Domain Services a paid service?](#is-azure-ad-domain-services-a-paid-service)

articles/active-directory/b2b/direct-federation.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ services: active-directory
66
ms.service: active-directory
77
ms.subservice: B2B
88
ms.topic: conceptual
9-
ms.date: 02/27/2019
9+
ms.date: 05/07/2020
1010

1111
ms.author: mimart
1212
author: msmimart
@@ -47,10 +47,13 @@ The domain you want to federate with must ***not*** be DNS-verified in Azure AD.
4747

4848
### Authentication URL
4949
Direct federation is only allowed for policies where the authentication URL’s domain matches the target domain, or where the authentication URL is one of these allowed identity providers (this list is subject to change):
50+
5051
- accounts.google.com
5152
- pingidentity.com
5253
- login.pingone.com
5354
- okta.com
55+
- oktapreview.com
56+
- okta-emea.com
5457
- my.salesforce.com
5558
- federation.exostar.com
5659
- federation.exostartest.com

articles/active-directory/conditional-access/service-dependencies.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,9 @@ With Conditional Access policies, you can specify access requirements to website
2222

2323
When you access a site or service directly, the impact of a related policy is typically easy to assess. For example, if you have a policy that requires multi-factor authentication (MFA) for SharePoint Online configured, MFA is enforced for each sign-in to the SharePoint web portal. However, it is not always straight-forward to assess the impact of a policy because there are cloud apps with dependencies to other cloud apps. For example, Microsoft Teams can provide access to resources in SharePoint Online. So, when you access Microsoft Teams in our current scenario, you are also subject to the SharePoint MFA policy.
2424

25+
> [!TIP]
26+
> Using the [Office 365 (preview)](concept-conditional-access-cloud-apps.md#office-365-preview) app will target all Office apps to avoid issues with service dependencies in the Office stack.
27+
2528
## Policy enforcement
2629

2730
If you have a service dependency configured, the policy may be applied using early-bound or late-bound enforcement.
Lines changed: 13 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
---
2-
title: Configure endpoints
3-
description: How to find the authentication endpoints for a custom application you are developing or registering with Azure AD.
2+
title: Get the endpoints for an Azure AD app registration
3+
titleSuffix: Microsoft identity platform
4+
description: How to find the authentication endpoints for a custom application you're developing or registering with Azure AD.
45
services: active-directory
56
author: rwike77
67
manager: CelesteDG
@@ -10,26 +11,24 @@ ms.subservice: develop
1011
ms.custom: aaddev
1112
ms.workload: identity
1213
ms.topic: conceptual
13-
ms.date: 07/15/2019
14+
ms.date: 05/07/2020
1415
ms.author: ryanwi
15-
1616
---
1717

18-
# How to configure endpoints
18+
# How to discover endpoints
1919

2020
You can find the authentication endpoints for your application in the [Azure portal](https://portal.azure.com).
2121

22-
- Navigate to the [Azure portal](https://portal.azure.com).
23-
24-
- From the left navigation pane, click **Azure Active Directory**.
25-
26-
- Click **App Registrations** and choose **Endpoints**.
22+
1. Sign in to the [Azure portal](https://portal.azure.com).
23+
1. Select **Azure Active Directory**.
24+
1. Under **Manage**, select **App registrations**, and then select **Endpoints** in the top menu.
2725

28-
- This open up the **Endpoints** page, which list all the authentication endpoints for your tenant.
29-
30-
- Use the endpoint specific to the authentication protocol you are using, in conjunction with the application ID to craft the authentication request specific to your application.
26+
The **Endpoints** page is displayed, showing the authentication endpoints for your tenant.
27+
28+
Use the endpoint that matches the authentication protocol you're using in conjunction with the **Application (client) ID** to craft the authentication request specific to your application.
3129

3230
**National clouds** (for example Azure AD China, Germany, and US Government) have their own app registration portal and Azure AD authentication endpoints. Learn more in the [National clouds overview](authentication-national-cloud.md).
3331

3432
## Next steps
35-
[Azure Active Directory developer's guide](https://docs.microsoft.com/azure/active-directory/develop/active-directory-developers-guide)
33+
34+
For more information about endpoints in the different Azure environments, see the [National clouds overview](authentication-national-cloud.md).

articles/active-directory/fundamentals/customize-branding.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.service: active-directory
99
ms.workload: identity
1010
ms.subservice: fundamentals
1111
ms.topic: conceptual
12-
ms.date: 09/18/2018
12+
ms.date: 05/07/2020
1313
ms.author: ajburnle
1414
ms.reviewer: kexia
1515
ms.custom: "it-pro, seodec18, fasttrack-edit"
@@ -48,17 +48,17 @@ Your custom branding won't immediately appear when your users go to sites such a
4848

4949
- **Language.** The language is automatically set as your default and can't be changed.
5050

51-
- **Sign-in page background image.** Select a .png or .jpg image file to appear as the background for your sign-in pages.
51+
- **Sign-in page background image.** Select a .png or .jpg image file to appear as the background for your sign-in pages. The image will be anchored to the center of the browser, and will scale to the size of the viewable space. You can't select an image larger than 1920x1080 pixels in size or that has a file size more than 300 KB.
5252

53-
The image can't be larger than 1920x1080 pixels in size and must have a file size of less than 300 KB.
53+
It's recommended to use images without a strong subject focus, e.g., an opaque white box appears in the center of the screen, and could cover any part of the image depending on the dimensions of the viewable space.
5454

5555
- **Banner logo.** Select a .png or .jpg version of your logo to appear on the sign-in page after the user enters a username and on the **My Apps** portal page.
5656

5757
The image can't be taller than 60 pixels or wider than 280 pixels. We recommend using a transparent image since the background might not match your logo background. We also recommend not adding padding around the image or it might make your logo look small.
5858

5959
- **Username hint.** Type the hint text that appears to users if they forget their username. This text must be Unicode, without links or code, and can't exceed 64 characters. If guests sign in to your app, we suggest not adding this hint.
6060

61-
- **Sign-in page text.** Type the text that appears on the bottom of the sign-in page. You can use this text to communicate additional information, such as the phone number to your help desk or a legal statement. This text must be Unicode and not exceed 256 characters. We also suggest not including links or HTML tags.
61+
- **Sign-in page text.** Type the text that appears on the bottom of the sign-in page. You can use this text to communicate additional information, such as the phone number to your help desk or a legal statement. This text must be Unicode and not exceed 256 characters.
6262

6363
- **Advanced settings**
6464

Lines changed: 171 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,171 @@
1+
---
2+
title: 'Tutorial: Azure Active Directory single sign-on (SSO) integration with EasySSO for Bamboo | Microsoft Docs'
3+
description: Learn how to configure single sign-on between Azure Active Directory and EasySSO for Bamboo.
4+
services: active-directory
5+
documentationCenter: na
6+
author: jeevansd
7+
manager: mtillman
8+
ms.reviewer: barbkess
9+
10+
ms.assetid: f594613d-0cd8-4046-a7c5-2da2971afecd
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/06/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 EasySSO for Bamboo
23+
24+
In this tutorial, you'll learn how to integrate EasySSO for Bamboo with Azure Active Directory (Azure AD). When you integrate EasySSO for Bamboo with Azure AD, you can:
25+
26+
* Control in Azure AD who has access to EasySSO for Bamboo.
27+
* Enable your users to be automatically signed-in to EasySSO for Bamboo 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+
* EasySSO for Bamboo 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+
* EasySSO for Bamboo supports **SP and IDP** initiated SSO
44+
* EasySSO for Bamboo supports **Just In Time** user provisioning
45+
* Once you configure EasySSO for Bamboo 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).
46+
47+
## Adding EasySSO for Bamboo from the gallery
48+
49+
To configure the integration of EasySSO for Bamboo into Azure AD, you need to add EasySSO for Bamboo from the gallery to your list of managed SaaS apps.
50+
51+
1. Sign in to the [Azure portal](https://portal.azure.com) using either a work or school account, or a personal Microsoft account.
52+
1. On the left navigation pane, select the **Azure Active Directory** service.
53+
1. Navigate to **Enterprise Applications** and then select **All Applications**.
54+
1. To add new application, select **New application**.
55+
1. In the **Add from the gallery** section, type **EasySSO for Bamboo** in the search box.
56+
1. Select **EasySSO for Bamboo** from results panel and then add the app. Wait a few seconds while the app is added to your tenant.
57+
58+
## Configure and test Azure AD single sign-on for EasySSO for Bamboo
59+
60+
Configure and test Azure AD SSO with EasySSO for Bamboo 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 EasySSO for Bamboo.
61+
62+
To configure and test Azure AD SSO with EasySSO for Bamboo, complete the following building blocks:
63+
64+
1. **[Configure Azure AD SSO](#configure-azure-ad-sso)** - to enable your users to use this feature.
65+
1. **[Create an Azure AD test user](#create-an-azure-ad-test-user)** - to test Azure AD single sign-on with B.Simon.
66+
1. **[Assign the Azure AD test user](#assign-the-azure-ad-test-user)** - to enable B.Simon to use Azure AD single sign-on.
67+
1. **[Configure EasySSO for Bamboo SSO](#configure-easysso-for-bamboo-sso)** - to configure the single sign-on settings on application side.
68+
1. **[Create EasySSO for Bamboo test user](#create-easysso-for-bamboo-test-user)** - to have a counterpart of B.Simon in EasySSO for Bamboo that is linked to the Azure AD representation of user.
69+
1. **[Test SSO](#test-sso)** - to verify whether the configuration works.
70+
71+
## Configure Azure AD SSO
72+
73+
Follow these steps to enable Azure AD SSO in the Azure portal.
74+
75+
1. In the [Azure portal](https://portal.azure.com/), on the **EasySSO for Bamboo** application integration page, find the **Manage** section and select **single sign-on**.
76+
1. On the **Select a single sign-on method** page, select **SAML**.
77+
1. On the **Set up single sign-on with SAML** page, click the edit/pen icon for **Basic SAML Configuration** to edit the settings.
78+
79+
![Edit Basic SAML Configuration](common/edit-urls.png)
80+
81+
1. On the **Basic SAML Configuration** section, if you wish to configure the application in **IDP** initiated mode, enter the values for the following fields:
82+
83+
a. In the **Identifier** text box, type a URL using the following pattern:
84+
`https://<server-base-url>/plugins/servlet/easysso/saml`
85+
86+
b. In the **Reply URL** text box, type a URL using the following pattern:
87+
`https://<server-base-url>/plugins/servlet/easysso/saml`
88+
89+
1. Click **Set additional URLs** and perform the following step if you wish to configure the application in **SP** initiated mode:
90+
91+
In the **Sign-on URL** text box, type a URL using the following pattern:
92+
`https://<server-base-url>/`
93+
94+
> [!NOTE]
95+
> These values are not real. Update these values with the actual Identifier, Reply URL and Sign-on URL. Contact [EasySSO for Bamboo 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.
96+
97+
1. EasySSO for Bamboo 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.
98+
99+
![image](common/default-attributes.png)
100+
101+
1. In addition to above, EasySSO for Bamboo 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.
102+
103+
| Name | Source Attribute |
104+
| ---------------| --------- |
105+
| urn:oid:2.16.840.1.113730.3.1.241 | user.displayname |
106+
| urn:oid:2.5.4.42 | user.givenname |
107+
| urn:oid:2.5.4.4 | user.surname |
108+
| urn:oid:0.9.2342.19200300.100.1.1 | user.userprincipalname |
109+
| urn:oid:0.9.2342.19200300.100.1.3 | user.userprincipalname |
110+
111+
1. On the **Set up single sign-on with SAML** page, In the **SAML Signing Certificate** section, click copy button to copy **App Federation Metadata Url** and save it on your computer.
112+
113+
![The Certificate download link](common/copy-metadataurl.png)
114+
115+
### Create an Azure AD test user
116+
117+
In this section, you'll create a test user in the Azure portal called B.Simon.
118+
119+
1. From the left pane in the Azure portal, select **Azure Active Directory**, select **Users**, and then select **All users**.
120+
1. Select **New user** at the top of the screen.
121+
1. In the **User** properties, follow these steps:
122+
1. In the **Name** field, enter `B.Simon`.
123+
1. In the **User name** field, enter the [email protected]. For example, `[email protected]`.
124+
1. Select the **Show password** check box, and then write down the value that's displayed in the **Password** box.
125+
1. Click **Create**.
126+
127+
### Assign the Azure AD test user
128+
129+
In this section, you'll enable B.Simon to use Azure single sign-on by granting access to EasySSO for Bamboo.
130+
131+
1. In the Azure portal, select **Enterprise Applications**, and then select **All applications**.
132+
1. In the applications list, select **EasySSO for Bamboo**.
133+
1. In the app's overview page, find the **Manage** section and select **Users and groups**.
134+
135+
![The "Users and groups" link](common/users-groups-blade.png)
136+
137+
1. Select **Add user**, then select **Users and groups** in the **Add Assignment** dialog.
138+
139+
![The Add User link](common/add-assign-user.png)
140+
141+
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.
142+
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.
143+
1. In the **Add Assignment** dialog, click the **Assign** button.
144+
145+
## Configure EasySSO for Bamboo SSO
146+
147+
To configure single sign-on on **EasySSO for Bamboo** side, you need to send the **App Federation Metadata Url** to [EasySSO for Bamboo support team](mailto:[email protected]). They set this setting to have the SAML SSO connection set properly on both sides.
148+
149+
### Create EasySSO for Bamboo test user
150+
151+
In this section, a user called Britta Simon is created in EasySSO for Bamboo. EasySSO for Bamboo supports just-in-time user provisioning, which is enabled by default. There is no action item for you in this section. If a user doesn't already exist in EasySSO for Bamboo, a new one is created after authentication.
152+
153+
## Test SSO
154+
155+
In this section, you test your Azure AD single sign-on configuration using the Access Panel.
156+
157+
When you click the EasySSO for Bamboo tile in the Access Panel, you should be automatically signed in to the EasySSO for Bamboo 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).
158+
159+
## Additional resources
160+
161+
- [ 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)
162+
163+
- [What is application access and single sign-on with Azure Active Directory? ](https://docs.microsoft.com/azure/active-directory/active-directory-appssoaccess-whatis)
164+
165+
- [What is conditional access in Azure Active Directory?](https://docs.microsoft.com/azure/active-directory/conditional-access/overview)
166+
167+
- [Try EasySSO for Bamboo with Azure AD](https://aad.portal.azure.com/)
168+
169+
- [What is session control in Microsoft Cloud App Security?](https://docs.microsoft.com/cloud-app-security/proxy-intro-aad)
170+
171+
- [How to protect EasySSO for Bamboo with advanced visibility and controls](https://docs.microsoft.com/cloud-app-security/proxy-intro-aad)

0 commit comments

Comments
 (0)