Skip to content

Commit a0f89fb

Browse files
Merge pull request #234210 from v-missam/cleanmail
update doc
2 parents 85589f1 + ccb18f5 commit a0f89fb

File tree

2 files changed

+28
-28
lines changed

2 files changed

+28
-28
lines changed

articles/active-directory/saas-apps/alinto-protect-provisioning-tutorial.md

Lines changed: 27 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: 'Tutorial: Configure Alinto Protect for automatic user provisioning with Azure Active Directory'
3-
description: Learn how to automatically provision and de-provision user accounts from Azure AD to Alinto Protect.
2+
title: 'Tutorial: Configure Cleanmail for automatic user provisioning with Azure Active Directory'
3+
description: Learn how to automatically provision and deprovision user accounts from Azure AD to Cleanmail.
44
services: active-directory
55
author: twimmers
66
writer: twimmers
@@ -14,61 +14,61 @@ ms.date: 11/21/2022
1414
ms.author: thwimmer
1515
---
1616

17-
# Tutorial: Configure Alinto Protect for automatic user provisioning
17+
# Tutorial: Configure Cleanmail for automatic user provisioning
1818

19-
This tutorial describes the steps you need to do in both Alinto Protect and Azure Active Directory (Azure AD) to configure automatic user provisioning. When configured, Azure AD automatically provisions and de-provisions users and groups to [Alinto Protect](https://www.alinto.com/) using the Azure AD Provisioning service. For important details on what this service does, how it works, and frequently asked questions, see [Automate user provisioning and deprovisioning to SaaS applications with Azure Active Directory](../app-provisioning/user-provisioning.md).
19+
This tutorial describes the steps you need to do in both Cleanmail and Azure Active Directory (Azure AD) to configure automatic user provisioning. When configured, Azure AD automatically provisions and deprovisions users and groups to [Cleanmail](https://www.alinto.com/) using the Azure AD Provisioning service. For important details on what this service does, how it works, and frequently asked questions, see [Automate user provisioning and deprovisioning to SaaS applications with Azure Active Directory](../app-provisioning/user-provisioning.md).
2020

2121

2222
## Capabilities supported
2323
> [!div class="checklist"]
24-
> * Create users in Alinto Protect
25-
> * Remove users in Alinto Protect when they do not require access anymore
26-
> * Keep user attributes synchronized between Azure AD and Alinto Protect
27-
> * [Single sign-on](../manage-apps/add-application-portal-setup-oidc-sso.md) to Alinto Protect (recommended).
24+
> * Create users in Cleanmail
25+
> * Remove users in Cleanmail when they do not require access anymore
26+
> * Keep user attributes synchronized between Azure AD and Cleanmail
27+
> * [Single sign-on](../manage-apps/add-application-portal-setup-oidc-sso.md) to Cleanmail (recommended).
2828
2929
## Prerequisites
3030

3131
The scenario outlined in this tutorial assumes that you already have the following prerequisites:
3232

3333
* [An Azure AD tenant](../develop/quickstart-create-new-tenant.md)
3434
* A user account in Azure AD with [permission](../roles/permissions-reference.md) to configure provisioning (for example, Application Administrator, Cloud Application administrator, Application Owner, or Global Administrator).
35-
* A user account in Alinto Protect with Admin permission
35+
* A user account in Cleanmail with Admin permission
3636

3737
## Step 1. Plan your provisioning deployment
3838
1. Learn about [how the provisioning service works](../app-provisioning/user-provisioning.md).
3939
1. Determine who will be in [scope for provisioning](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
40-
1. Determine what data to [map between Azure AD and Alinto Protect](../app-provisioning/customize-application-attributes.md).
40+
1. Determine what data to [map between Azure AD and Cleanmail](../app-provisioning/customize-application-attributes.md).
4141

42-
## Step 2. Configure Alinto Protect to support provisioning with Azure AD
42+
## Step 2. Configure Cleanmail to support provisioning with Azure AD
4343

44-
Contact [Alinto Protect Support](https://www.alinto.com/contact-email-provider/) to configure Alinto to support provisioning with Azure AD.
44+
Contact [Cleanmail Support](https://www.alinto.com/contact-email-provider/) to configure Alinto to support provisioning with Azure AD.
4545

46-
## Step 3. Add Alinto Protect from the Azure AD application gallery
46+
## Step 3. Add Cleanmail from the Azure AD application gallery
4747

48-
Add Alinto Protect from the Azure AD application gallery to start managing provisioning to Alinto Protect. If you have previously setup Alinto Protect for SSO, you can use the same application. However it's recommended you create a separate app when testing out the integration initially. Learn more about adding an application from the gallery [here](../manage-apps/add-application-portal.md).
48+
Add Cleanmail from the Azure AD application gallery to start managing provisioning to Cleanmail. If you have previously setup Cleanmail for SSO, you can use the same application. However it's recommended you create a separate app when testing out the integration initially. Learn more about adding an application from the gallery [here](../manage-apps/add-application-portal.md).
4949

5050
## Step 4. Define who will be in scope for provisioning
5151

5252
The Azure AD provisioning service allows you to scope who will be provisioned based on assignment to the application and or based on attributes of the user and group. If you choose to scope who will be provisioned to your app based on assignment, you can use the following [steps](../manage-apps/assign-user-or-group-access-portal.md) to assign users and groups to the application. If you choose to scope who will be provisioned based solely on attributes of the user or group, you can use a scoping filter as described [here](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
5353

5454
* Start small. Test with a small set of users and groups before rolling out to everyone. When scope for provisioning is set to assigned users and groups, you can control this by assigning one or two users or groups to the app. When scope is set to all users and groups, you can specify an [attribute based scoping filter](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
5555

56-
* If you need additional roles, you can [update the application manifest](../develop/howto-add-app-roles-in-azure-ad-apps.md) to add new roles.
56+
* If you need more roles, you can [update the application manifest](../develop/howto-add-app-roles-in-azure-ad-apps.md) to add new roles.
5757

5858

59-
## Step 5. Configure automatic user provisioning to Alinto Protect
59+
## Step 5. Configure automatic user provisioning to Cleanmail
6060

61-
This section guides you through the steps to configure the Azure AD provisioning service to create, update, and disable users and groups in Alinto Protect based on user and group assignments in Azure AD.
61+
This section guides you through the steps to configure the Azure AD provisioning service to create, update, and disable users and groups in Cleanmail based on user and group assignments in Azure AD.
6262

63-
### To configure automatic user provisioning for Alinto Protect in Azure AD:
63+
### To configure automatic user provisioning for Cleanmail in Azure AD:
6464

6565
1. Sign in to the [Azure portal](https://portal.azure.com). Select **Enterprise Applications**, then select **All applications**.
6666

6767
![Enterprise applications blade](common/enterprise-applications.png)
6868

69-
1. In the applications list, select **Alinto Protect**.
69+
1. In the applications list, select **Cleanmail**.
7070

71-
![The Alinto Protect link in the Applications list](common/all-applications.png)
71+
![The Cleanmail link in the Applications list](common/all-applications.png)
7272

7373
1. Select the **Provisioning** tab.
7474

@@ -78,7 +78,7 @@ This section guides you through the steps to configure the Azure AD provisioning
7878

7979
![Provisioning tab automatic](common/provisioning-automatic.png)
8080

81-
1. In the **Admin Credentials** section, input your Alinto Protect Tenant URL as `https://cloud.cleanmail.eu/api/v3/scim2` and corresponding Secret Token obtained from Step 2. Click **Test Connection** to ensure Azure AD can connect to Alinto Protect. If the connection fails, ensure your Alinto Protect account has Admin permissions and try again.
81+
1. In the **Admin Credentials** section, input your Cleanmail Tenant URL as `https://cloud.cleanmail.eu/api/v3/scim2` and corresponding Secret Token obtained from Step 2. Click **Test Connection** to ensure Azure AD can connect to Cleanmail. If the connection fails, ensure your Cleanmail account has Admin permissions and try again.
8282

8383
![Token](common/provisioning-testconnection-tenanturltoken.png)
8484

@@ -88,11 +88,11 @@ This section guides you through the steps to configure the Azure AD provisioning
8888

8989
1. Select **Save**.
9090

91-
1. In the **Mappings** section, select **Synchronize Azure Active Directory Users to Alinto Protect**.
91+
1. In the **Mappings** section, select **Synchronize Azure Active Directory Users to Cleanmail**.
9292

93-
1. Review the user attributes that are synchronized from Azure AD to Alinto Protect in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the user accounts in Alinto Protect for update operations. If you choose to change the [matching target attribute](../app-provisioning/customize-application-attributes.md), you'll need to ensure that the Alinto Protect API supports filtering users based on that attribute. Select the **Save** button to commit any changes.
93+
1. Review the user attributes that are synchronized from Azure AD to Cleanmail in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the user accounts in Cleanmail for update operations. If you choose to change the [matching target attribute](../app-provisioning/customize-application-attributes.md), you need to ensure that the Cleanmail API supports filtering users based on that attribute. Select the **Save** button to commit any changes.
9494

95-
|Attribute|Type|Supported for filtering|Required by Alinto Protect|
95+
|Attribute|Type|Supported for filtering|Required by Cleanmail|
9696
|---|---|---|---|
9797
|userName|String|✓|✓
9898
|active|Boolean||✓
@@ -102,11 +102,11 @@ This section guides you through the steps to configure the Azure AD provisioning
102102

103103
1. To configure scoping filters, refer to the following instructions provided in the [Scoping filter tutorial](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
104104

105-
1. To enable the Azure AD provisioning service for Alinto Protect, change the **Provisioning Status** to **On** in the **Settings** section.
105+
1. To enable the Azure AD provisioning service for Cleanmail, change the **Provisioning Status** to **On** in the **Settings** section.
106106

107107
![Provisioning Status Toggled On](common/provisioning-toggle-on.png)
108108

109-
1. Define the users and groups that you would like to provision to Alinto Protect by choosing the desired values in **Scope** in the **Settings** section.
109+
1. Define the users and groups that you would like to provision to Cleanmail by choosing the desired values in **Scope** in the **Settings** section.
110110

111111
![Provisioning Scope](common/provisioning-scope.png)
112112

@@ -121,7 +121,7 @@ Once you've configured provisioning, use the following resources to monitor your
121121

122122
* Use the [provisioning logs](../reports-monitoring/concept-provisioning-logs.md) to determine which users have been provisioned successfully or unsuccessfully
123123
* Check the [progress bar](../app-provisioning/application-provisioning-when-will-provisioning-finish-specific-user.md) to see the status of the provisioning cycle and how close it's to completion
124-
* If the provisioning configuration seems to be in an unhealthy state, the application will go into quarantine. Learn more about quarantine states [here](../app-provisioning/application-provisioning-quarantine-status.md).
124+
* If the provisioning configuration seems to be in an unhealthy state, the application goes into quarantine. Learn more about quarantine states [here](../app-provisioning/application-provisioning-quarantine-status.md).
125125

126126
## More resources
127127

articles/active-directory/saas-apps/toc.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2888,7 +2888,7 @@
28882888
href: alertmedia-provisioning-tutorial.md
28892889
- name: AlexisHR
28902890
href: alexishr-provisioning-tutorial.md
2891-
- name: Alinto Protect
2891+
- name: Alinto Protect (renamed Cleanmail)
28922892
href: alinto-protect-provisioning-tutorial.md
28932893
- name: ALVAO
28942894
href: alvao-provisioning-tutorial.md

0 commit comments

Comments
 (0)