Skip to content

Commit b902cf2

Browse files
v-missamv-missam
committed
doc-1
1 parent 080bb9a commit b902cf2

File tree

2 files changed

+178
-0
lines changed

2 files changed

+178
-0
lines changed

‎articles/active-directory/saas-apps/palo-alto-networks-scim-connector-provisioning-tutorial.md

Lines changed: 176 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,176 @@
1+
---
2+
title: 'Tutorial: Configure Palo Alto Networks SCIM Connector for automatic user provisioning with Azure Active Directory | Microsoft Docs'
3+
description: Learn how to automatically provision and de-provision user accounts from Azure AD to Palo Alto Networks SCIM Connector.
4+
services: active-directory
5+
documentationcenter: ''
6+
author: twimmers
7+
writer: Thwimmer
8+
manager: beatrizd
9+
10+
ms.assetid: b44885ef-fc1c-473c-9948-d7ca54d42d49
11+
ms.service: active-directory
12+
ms.subservice: saas-app-tutorial
13+
ms.workload: identity
14+
ms.devlang: na
15+
ms.topic: tutorial
16+
ms.date: 03/23/2022
17+
ms.author: Thwimmer
18+
---
19+
20+
# Tutorial: Configure Palo Alto Networks SCIM Connector for automatic user provisioning
21+
22+
This tutorial describes the steps you need to perform in both Palo Alto Networks SCIM Connector and Azure Active Directory (Azure AD) to configure automatic user provisioning. When configured, Azure AD automatically provisions and de-provisions users and groups to [Palo Alto Networks SCIM Connector](https://www.paloaltonetworks.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).
23+
24+
25+
## Capabilities supported
26+
> [!div class="checklist"]
27+
> * Create users in Palo Alto Networks SCIM Connector.
28+
> * Remove users in Palo Alto Networks SCIM Connector when they do not require access anymore.
29+
> * Keep user attributes synchronized between Azure AD and Palo Alto Networks SCIM Connector.
30+
> * Provision groups and group memberships in Palo Alto Networks SCIM Connector.
31+
32+
## Prerequisites
33+
34+
The scenario outlined in this tutorial assumes that you already have the following prerequisites:
35+
36+
* [An Azure AD tenant](../develop/quickstart-create-new-tenant.md).
37+
* 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).
38+
* A user account in Palo Alto Networks with Admin rights.
39+
40+
41+
## Step 1. Plan your provisioning deployment
42+
1. Learn about [how the provisioning service works](../app-provisioning/user-provisioning.md).
43+
1. Determine who will be in [scope for provisioning](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
44+
1. Determine what data to [map between Azure AD and Palo Alto Networks SCIM Connector](../app-provisioning/customize-application-attributes.md).
45+
46+
## Step 2. Configure Palo Alto Networks SCIM Connector to support provisioning with Azure AD
47+
48+
Contact [Palo Alto Networks Customer Support](https://support.paloaltonetworks.com/support) to obtain the **SCIM Url** and corresponding **Token**.
49+
50+
## Step 3. Add Palo Alto Networks SCIM Connector from the Azure AD application gallery
51+
52+
Add Palo Alto Networks SCIM Connector from the Azure AD application gallery to start managing provisioning to Palo Alto Networks SCIM Connector. If you have previously setup Palo Alto Networks SCIM Connector for SSO, you can use the same application. However it is 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).
53+
54+
## Step 4. Define who will be in scope for provisioning
55+
56+
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 / 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).
57+
58+
* When assigning users and groups to Palo Alto Networks SCIM Connector, you must select a role other than **Default Access**. Users with the Default Access role are excluded from provisioning and will be marked as not effectively entitled in the provisioning logs. If the only role available on the application is the default access role, you can [update the application manifest](../develop/howto-add-app-roles-in-azure-ad-apps.md) to add more roles.
59+
60+
* 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).
61+
62+
63+
## Step 5. Configure automatic user provisioning to Palo Alto Networks SCIM Connector
64+
65+
This section guides you through the steps to configure the Azure AD provisioning service to create, update, and disable users and/or groups in Palo Alto Networks SCIM Connector based on user and/or group assignments in Azure AD.
66+
67+
### To configure automatic user provisioning for Palo Alto Networks SCIM Connector in Azure AD:
68+
69+
1. Sign in to the [Azure portal](https://portal.azure.com). Select **Enterprise Applications**, then select **All applications**.
70+
71+
![Enterprise applications blade](common/enterprise-applications.png)
72+
73+
1. In the applications list, select **Palo Alto Networks SCIM Connector**.
74+
75+
![The Palo Alto Networks SCIM Connector link in the Applications list](common/all-applications.png)
76+
77+
1. Select the **Provisioning** tab.
78+
79+
![Provisioning tab](common/provisioning.png)
80+
81+
1. Set the **Provisioning Mode** to **Automatic**.
82+
83+
![Provisioning tab automatic](common/provisioning-automatic.png)
84+
85+
1. Under the **Admin Credentials** section, input your Palo Alto Networks SCIM Connector Tenant URL and Secret Token. Click **Test Connection** to ensure Azure AD can connect to Palo Alto Networks SCIM Connector. If the connection fails, ensure your Palo Alto Networks account has Admin permissions and try again.
86+
87+
![Token](common/provisioning-testconnection-tenanturltoken.png)
88+
89+
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.
90+
91+
![Notification Email](common/provisioning-notification-email.png)
92+
93+
1. Select **Save**.
94+
95+
1. Under the **Mappings** section, select **Synchronize Azure Active Directory Users to Palo Alto Networks SCIM Connector**.
96+
97+
1. Review the user attributes that are synchronized from Azure AD to Palo Alto Networks SCIM Connector in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the user accounts in Palo Alto Networks SCIM Connector for update operations. If you choose to change the [matching target attribute](../app-provisioning/customize-application-attributes.md), you will need to ensure that the Palo Alto Networks SCIM Connector API supports filtering users based on that attribute. Select the **Save** button to commit any changes.
98+
99+
|Attribute|Type|Supported for filtering|Required by Palo Alto Networks SCIM Connector|
100+
|---|---|---|---|
101+
|userName|String|✓|✓
102+
|active|Boolean||✓
103+
|displayName|String||✓
104+
|title|String||
105+
|emails[type eq "work"].value|String||
106+
|emails[type eq "other"].value|String||
107+
|preferredLanguage|String||
108+
|name.givenName|String||✓
109+
|name.familyName|String||✓
110+
|name.formatted|String||✓
111+
|name.honorificSuffix|String||
112+
|name.honorificPrefix|String||
113+
|addresses[type eq "work"].formatted|String||
114+
|addresses[type eq "work"].streetAddress|String||
115+
|addresses[type eq "work"].locality|String||
116+
|addresses[type eq "work"].region|String||
117+
|addresses[type eq "work"].postalCode|String||
118+
|addresses[type eq "work"].country|String||
119+
|addresses[type eq "other"].formatted|String||
120+
|addresses[type eq "other"].streetAddress|String||
121+
|addresses[type eq "other"].locality|String||
122+
|addresses[type eq "other"].region|String||
123+
|addresses[type eq "other"].postalCode|String||
124+
|addresses[type eq "other"].country|String||
125+
|phoneNumbers[type eq "work"].value|String||
126+
|phoneNumbers[type eq "mobile"].value|String||
127+
|phoneNumbers[type eq "fax"].value|String||
128+
|externalId|String||
129+
|urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:employeeNumber|String||
130+
|urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:department|String||
131+
|urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:manager|String||
132+
133+
>![NOTE]
134+
>**Schema Discovery** is enabled on this app. Hence you might see more attributes in the application than mentioned in the table above.
135+
136+
1. Under the **Mappings** section, select **Synchronize Azure Active Directory Groups to Palo Alto Networks SCIM Connector**.
137+
138+
1. Review the group attributes that are synchronized from Azure AD to Palo Alto Networks SCIM Connector in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the groups in Palo Alto Networks SCIM Connector for update operations. Select the **Save** button to commit any changes.
139+
140+
|Attribute|Type|Supported for filtering|Required by Palo Alto Networks SCIM Connector|
141+
|---|---|---|---|
142+
|displayName|String|✓|✓
143+
|members|Reference||
144+
145+
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).
146+
147+
1. To enable the Azure AD provisioning service for Palo Alto Networks SCIM Connector, change the **Provisioning Status** to **On** in the **Settings** section.
148+
149+
![Provisioning Status Toggled On](common/provisioning-toggle-on.png)
150+
151+
1. Define the users and/or groups that you would like to provision to Palo Alto Networks SCIM Connector by choosing the desired values in **Scope** in the **Settings** section.
152+
153+
![Provisioning Scope](common/provisioning-scope.png)
154+
155+
1. When you are ready to provision, click **Save**.
156+
157+
![Saving Provisioning Configuration](common/provisioning-configuration-save.png)
158+
159+
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 Azure AD provisioning service is running.
160+
161+
## Step 6. Monitor your deployment
162+
Once you've configured provisioning, use the following resources to monitor your deployment:
163+
164+
* Use the [provisioning logs](../reports-monitoring/concept-provisioning-logs.md) to determine which users have been provisioned successfully or unsuccessfully
165+
* 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 is to completion
166+
* 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).
167+
168+
169+
## More resources
170+
171+
* [Managing user account provisioning for Enterprise Apps](../app-provisioning/configure-automatic-user-provisioning-portal.md)
172+
* [What is application access and single sign-on with Azure Active Directory?](../manage-apps/what-is-single-sign-on.md)
173+
174+
## Next steps
175+
176+
* [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: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2781,6 +2781,8 @@
27812781
href: oracle-cloud-infrastructure-console-provisioning-tutorial.md
27822782
- name: Oracle Fusion ERP
27832783
href: oracle-fusion-erp-provisioning-tutorial.md
2784+
- name: Palo Alto Networks SCIM Connector
2785+
href: palo-alto-networks-scim-connector-provisioning-tutorial.md
27842786
- name: PaperCut Cloud Print Management
27852787
href: papercut-cloud-print-management-provisioning-tutorial.md
27862788
- name: Parsable

0 commit comments

Comments
 (0)