Skip to content

Commit 6c59463

Browse files
PMEds28PMEds28
authored
Merge pull request #253709 from Harshita-130901/Screensteps-and-open-text-provisioning-tutorials
Screensteps and open text
2 parents b9834b0 + 9d88caa commit 6c59463

File tree

3 files changed

+298
-0
lines changed

3 files changed

+298
-0
lines changed

‎articles/active-directory/saas-apps/screensteps-provisioning-tutorial.md

Lines changed: 148 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,148 @@
1+
---
2+
title: 'Tutorial: Configure ScreenSteps for automatic user provisioning with Microsoft Entra ID'
3+
description: Learn how to automatically provision and deprovision user accounts from Microsoft Entra ID to ScreenSteps.
4+
services: active-directory
5+
author: twimmers
6+
writer: twimmers
7+
manager: jeedes
8+
ms.assetid: e6e21ae5-f1d4-479c-b5d9-1377a85ecb71
9+
ms.service: active-directory
10+
ms.subservice: saas-app-tutorial
11+
ms.workload: identity
12+
ms.topic: tutorial
13+
ms.date: 10/04/2023
14+
ms.author: thwimmer
15+
---
16+
17+
# Tutorial: Configure ScreenSteps for automatic user provisioning
18+
19+
This tutorial describes the steps you need to perform in both ScreenSteps and Microsoft Entra ID to configure automatic user provisioning. When configured, Microsoft Entra ID automatically provisions and deprovisions users and groups to [ScreenSteps](http://www.screensteps.com/) using the Microsoft Entra 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 Microsoft Entra ID](../app-provisioning/user-provisioning.md).
20+
21+
## Supported capabilities
22+
> [!div class="checklist"]
23+
> * Create users in ScreenSteps.
24+
> * Remove users in ScreenSteps when they do not require access anymore.
25+
> * Keep user attributes synchronized between Microsoft Entra ID and ScreenSteps.
26+
> * Provision groups and group memberships in ScreenSteps.
27+
> * [Single sign-on](screensteps-tutorial.md) to ScreenSteps (recommended).
28+
29+
## Prerequisites
30+
31+
The scenario outlined in this tutorial assumes that you already have the following prerequisites:
32+
33+
* [A Microsoft Entra tenant](../develop/quickstart-create-new-tenant.md)
34+
* A user account in Microsoft Entra ID 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 ScreenSteps with Admin permissions.
36+
37+
## Step 1: Plan your provisioning deployment
38+
1. Learn about [how the provisioning service works](../app-provisioning/user-provisioning.md).
39+
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 Microsoft Entra ID and ScreenSteps](../app-provisioning/customize-application-attributes.md).
41+
42+
<a name='step-2-configure-ScreenSteps-to-support-provisioning-with-azure-ad'></a>
43+
44+
## Step 2: Configure ScreenSteps to support provisioning with Microsoft Entra ID
45+
Contact ScreenSteps support to configure ScreenSteps to support provisioning with Microsoft Entra ID.
46+
47+
<a name='step-3-add-ScreenSteps-from-the-azure-ad-application-gallery'></a>
48+
49+
## Step 3: Add ScreenSteps from the Microsoft Entra application gallery
50+
51+
Add ScreenSteps from the Microsoft Entra application gallery to start managing provisioning to ScreenSteps. If you have previously set up ScreenSteps for SSO you can use the same application. However, it's recommended that 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).
52+
53+
## Step 4: Define who will be in scope for provisioning
54+
55+
The Microsoft Entra provisioning service allows you to scope who will be provisioned based on assignment to the application and or based on attributes of the user / 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).
56+
57+
* Start small. Test with a small set of users and groups before rolling out to everyone. When the 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 the 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).
58+
59+
* 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.
60+
61+
## Step 5: Configure automatic user provisioning to ScreenSteps
62+
63+
This section guides you through the steps to configure the Microsoft Entra provisioning service to create, update, and disable users and/or groups in TestApp based on user and/or group assignments in Microsoft Entra ID.
64+
65+
<a name='to-configure-automatic-user-provisioning-for-ScreenSteps-in-azure-ad'></a>
66+
67+
### To configure automatic user provisioning for ScreenSteps in Microsoft Entra ID:
68+
69+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Cloud Application Administrator](../roles/permissions-reference.md#cloud-application-administrator).
70+
1. Browse to **Identity** > **Applications** > **Enterprise applications**
71+
72+
![Screenshot of Enterprise applications blade.](common/enterprise-applications.png)
73+
74+
1. In the applications list, select **ScreenSteps**.
75+
76+
![Screenshot of the ScreenSteps link in the Applications list.](common/all-applications.png)
77+
78+
1. Select the **Provisioning** tab.
79+
80+
![Screenshot of Provisioning tab.](common/provisioning.png)
81+
82+
1. Set the **Provisioning Mode** to **Automatic**.
83+
84+
![Screenshot of Provisioning tab automatic.](common/provisioning-automatic.png)
85+
86+
1. Under the **Admin Credentials** section, input your ScreenSteps Tenant URL and Secret Token. Click **Test Connection** to ensure Microsoft Entra ID can connect to ScreenSteps. If the connection fails, ensure your ScreenSteps account has Admin permissions and try again.
87+
88+
![Screenshot of Token.](common/provisioning-testconnection-tenanturltoken.png)
89+
90+
1. In the **Notification Email** field, enter the email address of a person or group who should receive the provisioning error notifications and select the **Send an email notification when a failure occurs** check box.
91+
92+
![Screenshot of Notification Email.](common/provisioning-notification-email.png)
93+
94+
1. Select **Save**.
95+
96+
1. Under the **Mappings** section, select **Synchronize Microsoft Entra users to ScreenSteps**.
97+
98+
1. Review the user attributes that are synchronized from Microsoft Entra ID to ScreenSteps in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the user accounts in ScreenSteps 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 ScreenSteps API supports filtering users based on that attribute. Select the **Save** button to commit any changes.
99+
100+
|Attribute|Type|Supported for filtering|Required by ScreenSteps|
101+
|---|---|---|---|
102+
|userName|String|&check;|&check;
103+
|emails[type eq "work"].value|String||
104+
|name.givenName|String||
105+
|name.familyName|String||
106+
|externalId|String||
107+
108+
1. Under the **Mappings** section, select **Synchronize Microsoft Entra groups to ScreenSteps**.
109+
110+
1. Review the group attributes that are synchronized from Microsoft Entra ID to ScreenSteps in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the groups in ScreenSteps for update operations. Select the **Save** button to commit any changes.
111+
112+
|Attribute|Type|Supported for filtering|Required by ScreenSteps|
113+
|---|---|---|---|
114+
|displayName|String|&check;|&check;
115+
|members|Reference||
116+
|externalId|String||
117+
118+
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).
119+
120+
1. To enable the Microsoft Entra provisioning service for ScreenSteps, change the **Provisioning Status** to **On** in the **Settings** section.
121+
122+
![Screenshot of Provisioning Status Toggled On.](common/provisioning-toggle-on.png)
123+
124+
1. Define the users and/or groups that you would like to provision to ScreenSteps by choosing the desired values in **Scope** in the **Settings** section.
125+
126+
![Screenshot of Provisioning Scope.](common/provisioning-scope.png)
127+
128+
1. When you're ready to provision, click **Save**.
129+
130+
![Screenshot of Saving Provisioning Configuration.](common/provisioning-configuration-save.png)
131+
132+
This operation starts the initial synchronization cycle of all users and groups defined in **Scope** in the **Settings** section. The initial cycle takes longer to perform than subsequent cycles, which occur approximately every 40 minutes as long as the Microsoft Entra provisioning service is running.
133+
134+
## Step 6: Monitor your deployment
135+
Once you've configured provisioning, use the following resources to monitor your deployment:
136+
137+
* Use the [provisioning logs](../reports-monitoring/concept-provisioning-logs.md) to determine which users have been provisioned successfully or unsuccessfully.
138+
* 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.
139+
* 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).
140+
141+
## More resources
142+
143+
* [Managing user account provisioning for Enterprise Apps](../app-provisioning/configure-automatic-user-provisioning-portal.md).
144+
* [What is application access and single sign-on with Microsoft Entra ID?](../manage-apps/what-is-single-sign-on.md).
145+
146+
## Next steps
147+
148+
* [Learn how to review logs and get reports on provisioning activity](../app-provisioning/check-status-user-account-provisioning.md).

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

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3466,6 +3466,8 @@
34663466
href: sap-successfactors-writeback-tutorial.md
34673467
- name: SchoolStream ASA
34683468
href: schoolstream-asa-provisioning-tutorial.md
3469+
- name: ScreenSteps
3470+
href: screensteps-provisioning-tutorial.md
34693471
- name: SECURE DELIVER
34703472
href: secure-deliver-provisioning-tutorial.md
34713473
- name: SecureLogin
@@ -3610,6 +3612,8 @@
36103612
href: wrike-provisioning-tutorial.md
36113613
- name: Xledger
36123614
href: xledger-provisioning-tutorial.md
3615+
- name: XM Fax and XM SendSecure
3616+
href: xm-fax-and-xm-send-secure-provisioning-tutorial.md
36133617
- name: Yellowbox
36143618
href: yellowbox-provisioning-tutorial.md
36153619
- name: Zapier

0 commit comments

Comments
 (0)