You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory/hybrid/concept-azure-ad-connect-sync-architecture.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -170,6 +170,8 @@ When sync engine finds a staging object that matches by distinguished name but n
170
170
* If the object located in the connector space has no anchor, then sync engine removes this object from the connector space and marks the metaverse object it is linked to as **retry provisioning on next synchronization run**. Then it creates the new import object.
171
171
* If the object located in the connector space has an anchor, then sync engine assumes that this object has either been renamed or deleted in the connected directory. It assigns a temporary, new distinguished name for the connector space object so that it can stage the incoming object. The old object then becomes **transient**, waiting for the Connector to import the rename or deletion to resolve the situation.
172
172
173
+
Transient objects are not always a problem, and you might see them even in a healthy environment. With [Azure AD Connect sync V2 endpoint API](how-to-connect-sync-endpoint-api-v2.md), transient objects should auto-resolve in subsequent delta synchronization cycles. A common example where you might find transient objects being generated occurs on Azure AD Connect servers installed in staging mode, when an admin permanently deletes an object directly in Azure AD using PowerShell and later synchronizes the object again.
174
+
173
175
If sync engine locates a staging object that corresponds to the object specified in the Connector, it determines what kind of changes to apply. For example, sync engine might rename or delete the object in the connected data source, or it might only update the object’s attribute values.
174
176
175
177
Staging objects with updated data are marked as pending import. Different types of pending imports are available. Depending on the result of the import process, a staging object in the connector space has one of the following pending import types:
title: 'Tutorial: Azure AD SSO integration with BetterWorks'
3
-
description: Learn how to configure single sign-on between Azure Active Directory and BetterWorks.
2
+
title: 'Tutorial: Azure AD SSO integration with Betterworks'
3
+
description: Learn how to configure single sign-on between Azure Active Directory and Betterworks.
4
4
services: active-directory
5
5
author: jeevansd
6
6
manager: CelesteDG
@@ -13,59 +13,59 @@ ms.date: 10/07/2021
13
13
ms.author: jeedes
14
14
---
15
15
16
-
# Tutorial: Azure AD SSO integration with BetterWorks
16
+
# Tutorial: Azure AD SSO integration with Betterworks
17
17
18
-
In this tutorial, you'll learn how to integrate BetterWorks with Azure Active Directory (Azure AD). When you integrate BetterWorks with Azure AD, you can:
18
+
In this tutorial, you'll learn how to integrate Betterworks with Azure Active Directory (Azure AD). When you integrate Betterworks with Azure AD, you can:
19
19
20
-
* Control in Azure AD who has access to BetterWorks.
21
-
* Enable your users to be automatically signed-in to BetterWorks with their Azure AD accounts.
20
+
* Control in Azure AD who has access to Betterworks.
21
+
* Enable your users to be automatically signed-in to Betterworks with their Azure AD accounts.
22
22
* Manage your accounts in one central location - the Azure portal.
23
23
24
24
## Prerequisites
25
25
26
26
To get started, you need the following items:
27
27
28
28
* An Azure AD subscription. If you don't have a subscription, you can get a [free account](https://azure.microsoft.com/free/).
29
-
*BetterWorks single sign-on (SSO) enabled subscription.
29
+
*Betterworks single sign-on (SSO) enabled subscription.
30
30
31
31
## Scenario description
32
32
33
33
In this tutorial, you configure and test Azure AD SSO in a test environment.
34
34
35
-
*BetterWorks supports **SP and IDP** initiated SSO.
35
+
*Betterworks supports **SP and IDP** initiated SSO.
36
36
37
37
> [!NOTE]
38
38
> Identifier of this application is a fixed string value so only one instance can be configured in one tenant.
39
39
40
-
## Add BetterWorks from the gallery
40
+
## Add Betterworks from the gallery
41
41
42
-
To configure the integration of BetterWorks into Azure AD, you need to add BetterWorks from the gallery to your list of managed SaaS apps.
42
+
To configure the integration of Betterworks into Azure AD, you need to add Betterworks from the gallery to your list of managed SaaS apps.
43
43
44
44
1. Sign in to the Azure portal using either a work or school account, or a personal Microsoft account.
45
45
1. On the left navigation pane, select the **Azure Active Directory** service.
46
46
1. Navigate to **Enterprise Applications** and then select **All Applications**.
47
47
1. To add new application, select **New application**.
48
-
1. In the **Add from the gallery** section, type **BetterWorks** in the search box.
49
-
1. Select **BetterWorks** from results panel and then add the app. Wait a few seconds while the app is added to your tenant.
48
+
1. In the **Add from the gallery** section, type **Betterworks** in the search box.
49
+
1. Select **Betterworks** from results panel and then add the app. Wait a few seconds while the app is added to your tenant.
50
50
51
-
## Configure and test Azure AD SSO for BetterWorks
51
+
## Configure and test Azure AD SSO for Betterworks
52
52
53
-
Configure and test Azure AD SSO with BetterWorks 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 BetterWorks.
53
+
Configure and test Azure AD SSO with Betterworks 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 Betterworks.
54
54
55
-
To configure and test Azure AD SSO with BetterWorks, perform the following steps:
55
+
To configure and test Azure AD SSO with Betterworks, perform the following steps:
56
56
57
57
1.**[Configure Azure AD SSO](#configure-azure-ad-sso)** - to enable your users to use this feature.
58
58
1.**[Create an Azure AD test user](#create-an-azure-ad-test-user)** - to test Azure AD single sign-on with B.Simon.
59
59
1.**[Assign the Azure AD test user](#assign-the-azure-ad-test-user)** - to enable B.Simon to use Azure AD single sign-on.
60
-
1.**[Configure BetterWorks SSO](#configure-betterworks-sso)** - to configure the single sign-on settings on application side.
61
-
1.**[Create BetterWorks test user](#create-betterworks-test-user)** - to have a counterpart of B.Simon in BetterWorks that is linked to the Azure AD representation of user.
60
+
1.**[Configure Betterworks SSO](#configure-betterworks-sso)** - to configure the single sign-on settings on application side.
61
+
1.**[Create Betterworks test user](#create-betterworks-test-user)** - to have a counterpart of B.Simon in Betterworks that is linked to the Azure AD representation of user.
62
62
1.**[Test SSO](#test-sso)** - to verify whether the configuration works.
63
63
64
64
## Configure Azure AD SSO
65
65
66
66
Follow these steps to enable Azure AD SSO in the Azure portal.
67
67
68
-
1. In the Azure portal, on the **BetterWorks** application integration page, find the **Manage** section and select **single sign-on**.
68
+
1. In the Azure portal, on the **Betterworks** application integration page, find the **Manage** section and select **single sign-on**.
69
69
1. On the **Select a single sign-on method** page, select **SAML**.
70
70
1. On the **Set up single sign-on with SAML** page, click the pencil icon for **Basic SAML Configuration** to edit the settings.
71
71
@@ -85,13 +85,13 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
85
85
`https://app.betterworks.com`
86
86
87
87
> [!NOTE]
88
-
> If you're a European Union customer of BetterWorks, please use `eu.betterworks.com` as the domain name instead of `app.betterworks.com` in these URLs.
88
+
> If you're a European Union customer of Betterworks, please use `eu.betterworks.com` as the domain name instead of `app.betterworks.com` in these URLs.
89
89
90
90
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,40 +109,40 @@ In this section, you'll create a test user in the Azure portal called B.Simon.
109
109
110
110
### Assign the Azure AD test user
111
111
112
-
In this section, you'll enable B.Simon to use Azure single sign-on by granting access to BetterWorks.
112
+
In this section, you'll enable B.Simon to use Azure single sign-on by granting access to Betterworks.
113
113
114
114
1. In the Azure portal, select **Enterprise Applications**, and then select **All applications**.
115
-
1. In the applications list, select **BetterWorks**.
115
+
1. In the applications list, select **Betterworks**.
116
116
1. In the app's overview page, find the **Manage** section and select **Users and groups**.
117
117
1. Select **Add user**, then select **Users and groups** in the **Add Assignment** dialog.
118
118
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.
119
119
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.
120
120
1. In the **Add Assignment** dialog, click the **Assign** button.
121
121
122
-
## Configure BetterWorks SSO
122
+
## Configure Betterworks SSO
123
123
124
-
To configure single sign-on on **BetterWorks** side, you need to send the downloaded **Federation Metadata XML** and appropriate copied URLs from Azure portal to [BetterWorks support team](mailto:[email protected]). They set this setting to have the SAML SSO connection set properly on both sides.
124
+
To configure single sign-on on **Betterworks** side, you need to send the downloaded **Federation Metadata XML** and appropriate copied URLs from Azure portal to [Betterworks support team](mailto:[email protected]). They set this setting to have the SAML SSO connection set properly on both sides.
125
125
126
-
### Create BetterWorks test user
126
+
### Create Betterworks test user
127
127
128
-
In this section, you create a user called Britta Simon in BetterWorks. Work with [BetterWorks support team](mailto:[email protected]) to add the users in the BetterWorks platform. Users must be created and activated before you use single sign-on.
128
+
In this section, you create a user called Britta Simon in Betterworks. Work with [Betterworks support team](mailto:[email protected]) to add the users in the Betterworks platform. Users must be created and activated before you use single sign-on.
129
129
130
130
## Test SSO
131
131
132
132
In this section, you test your Azure AD single sign-on configuration with following options.
133
133
134
134
#### SP initiated:
135
135
136
-
* Click on **Test this application** in Azure portal. This will redirect to BetterWorks Sign on URL where you can initiate the login flow.
136
+
* Click on **Test this application** in Azure portal. This will redirect to Betterworks Sign on URL where you can initiate the login flow.
137
137
138
-
* Go to BetterWorks Sign-on URL directly and initiate the login flow from there.
138
+
* Go to Betterworks Sign-on URL directly and initiate the login flow from there.
139
139
140
140
#### IDP initiated:
141
141
142
-
* Click on **Test this application** in Azure portal and you should be automatically signed in to the BetterWorks for which you set up the SSO.
142
+
* Click on **Test this application** in Azure portal and you should be automatically signed in to the Betterworks for which you set up the SSO.
143
143
144
-
You can also use Microsoft My Apps to test the application in any mode. When you click the BetterWorks tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the BetterWorks for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md).
144
+
You can also use Microsoft My Apps to test the application in any mode. When you click the Betterworks tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Betterworks for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md).
145
145
146
146
## Next steps
147
147
148
-
Once you configure BetterWorks you can enforce session control, which protects exfiltration and infiltration of your organization’s sensitive data in real time. Session control extends from Conditional Access. [Learn how to enforce session control with Microsoft Defender for Cloud Apps](/cloud-app-security/proxy-deployment-aad).
148
+
Once you configure Betterworks you can enforce session control, which protects exfiltration and infiltration of your organization’s sensitive data in real time. Session control extends from Conditional Access. [Learn how to enforce session control with Microsoft Defender for Cloud Apps](/cloud-app-security/proxy-deployment-aad).
Submit the `config.txt` file with this invocation: `msgen submit -f config.txt`
79
79
80
80
## Next steps
81
-
In this article, you uploaded a BAM file into Azure Storage and submitted a workflow to the Microsoft Genomics service through the `msgen`python client. For additional information regarding workflow submission and other commands you can use with the Microsoft Genomics service, see our [FAQ](frequently-asked-questions-genomics.yml).
81
+
In this article, you uploaded a BAM file into Azure Storage and submitted a workflow to the Microsoft Genomics service through the `msgen`Python client. For additional information regarding workflow submission and other commands you can use with the Microsoft Genomics service, see our [FAQ](frequently-asked-questions-genomics.yml).
Submit the `config.txt` file with this invocation: `msgen submit -f config.txt`
153
153
154
154
## Next steps
155
-
In this article, you uploaded multiple BAM files or paired FASTQ files into Azure Storage and submitted a workflow to the Microsoft Genomics service through the `msgen`python client. For more information regarding workflow submission and other commands you can use with the Microsoft Genomics service, see the [FAQ](frequently-asked-questions-genomics.yml).
155
+
In this article, you uploaded multiple BAM files or paired FASTQ files into Azure Storage and submitted a workflow to the Microsoft Genomics service through the `msgen`Python client. For more information regarding workflow submission and other commands you can use with the Microsoft Genomics service, see the [FAQ](frequently-asked-questions-genomics.yml).
Submit the `config.txt` file with this invocation: `msgen submit -f config.txt`
79
79
80
80
## Next steps
81
-
In this article, you uploaded a pair of FASTQ files into Azure Storage and submitted a workflow to the Microsoft Genomics service through the `msgen`python client. To learn more about workflow submission and other commands you can use with the Microsoft Genomics service, see our [FAQ](frequently-asked-questions-genomics.yml).
81
+
In this article, you uploaded a pair of FASTQ files into Azure Storage and submitted a workflow to the Microsoft Genomics service through the `msgen`Python client. To learn more about workflow submission and other commands you can use with the Microsoft Genomics service, see our [FAQ](frequently-asked-questions-genomics.yml).
0 commit comments