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/saas-apps/jostle-provisioning-tutorial.md
+7-4Lines changed: 7 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -92,6 +92,9 @@ The Azure AD provisioning service allows you to scope who will be provisioned ba
92
92
93
93
This section guides you through the steps to configure the Azure AD provisioning service to create, update, and disable users and groups in Jostle app based on user and group assignments in Azure AD.
94
94
95
+
> [!NOTE]
96
+
> For more information on automatic user provisioning to Jostle, see [User-Provisioning-Azure-Integration](https://forum.jostle.us/hc/en-us/articles/360056368534-User-Provisioning-Azure-Integration).
97
+
95
98
### To configure automatic user provisioning for Jostle in Azure AD:
96
99
97
100
1. Sign in to the [Azure portal](https://portal.azure.com). Select **Enterprise Applications**, then select **All applications**.
@@ -102,7 +105,7 @@ This section guides you through the steps to configure the Azure AD provisioning
102
105
103
106
104
107
105
-
1. Select the **Provisioning** tab.
108
+
1. Select the **Provisioning** tab and click **Get Started**.
106
109
107
110
108
111
@@ -114,13 +117,13 @@ This section guides you through the steps to configure the Azure AD provisioning
1. In the **Notification Email** field, enter the email address of a person or group who should receive the provisioning error notifications. Select the **Send an email notification when a failure occurs** check box.
120
+
1. In the **Notification Email** field, enter the email address of a person or group who should receive the provisioning error notifications. Select the **Send an email notification when a failure occurs** check box. But to be noted, Jostle will also send provisioning failure notifications, so this is optional.
1. In the **Mappings** section, select **Synchronize Azure Active Directory Users to Jostle**.
126
+
1. In the **Mappings** section, select **Provision Azure Active Directory Users to Jostle**.
124
127
125
128
1. Review the user attributes that are synchronized from Azure AD to Jostle in the **Attribute Mapping** section. The attributes selected as **Matching** properties are used to match the user accounts in Jostle for update operations. If you change the [matching target attribute](../app-provisioning/customize-application-attributes.md), you'll need to ensure that the Jostle API supports filtering users based on that attribute. Select **Save** to commit any changes.
126
129
@@ -143,7 +146,7 @@ This section guides you through the steps to configure the Azure AD provisioning
143
146
144
147
145
148
146
-
1. Define the users or groups that you want to provision to Jostle by selecting the desired values in **Scope** in the **Settings** section.
149
+
1. Define the users or groups that you want to provision to Jostle by selecting the desired values in **Scope** in the **Settings** section.For Jostle, the **Scope** should be set to "Sync only assigned users and groups".
Copy file name to clipboardExpand all lines: articles/active-directory/saas-apps/purecloud-by-genesys-provisioning-tutorial.md
+22-12Lines changed: 22 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,7 +31,7 @@ This tutorial describes the steps you need to perform in both PureCloud by Genes
31
31
The scenario outlined in this tutorial assumes that you already have the following prerequisites:
32
32
33
33
*[An Azure AD tenant](../develop/quickstart-create-new-tenant.md)
34
-
* A user account in Azure AD with [permission](../roles/permissions-reference.md) to configure provisioning (e.g. Application Administrator, Cloud Application administrator, Application Owner, or Global Administrator).
34
+
* 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
35
* A PureCloud [organization](https://help.mypurecloud.com/?p=81984).
36
36
* A User with [permissions](https://help.mypurecloud.com/?p=24360) to create an Oauth Client.
37
37
@@ -48,7 +48,7 @@ The scenario outlined in this tutorial assumes that you already have the followi
48
48
49
49
## Step 3. Add PureCloud by Genesys from the Azure AD application gallery
50
50
51
-
Add PureCloud by Genesys from the Azure AD application gallery to start managing provisioning to PureCloud by Genesys. If you have previously setup PureCloud by Genesys 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).
51
+
Add PureCloud by Genesys from the Azure AD application gallery to start managing provisioning to PureCloud by Genesys. If you have previously setup PureCloud by Genesys 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).
52
52
53
53
## Step 4. Define who will be in scope for provisioning
54
54
@@ -81,7 +81,7 @@ This section guides you through the steps to configure the Azure AD provisioning
81
81
82
82
83
83
84
-
5. Under the **Admin Credentials** section, input your PureCloud by Genesys API URL and Oauth Token in the **Tenant URL** and **Secret Token** fields respectively. The API URL will be be structured as `{{API Url}}/api/v2/scim/v2`, using the API URL for your PureCloud region from the [PureCloud Developer Center](https://developer.mypurecloud.com/api/rest/index.html). Click **Test Connection** to ensure Azure AD can connect to PureCloud by Genesys. If the connection fails, ensure your PureCloud by Genesys account has Admin permissions and try again.
84
+
5. Under the **Admin Credentials** section, input your PureCloud by Genesys API URL and Oauth Token in the **Tenant URL** and **Secret Token** fields respectively. The API URL will be structured as `{{API Url}}/api/v2/scim/v2`, using the API URL for your PureCloud region from the [PureCloud Developer Center](https://developer.mypurecloud.com/api/rest/index.html). Click **Test Connection** to ensure Azure AD can connect to PureCloud by Genesys. If the connection fails, ensure your PureCloud by Genesys account has Admin permissions and try again.
85
85
86
86
87
87
@@ -95,27 +95,36 @@ This section guides you through the steps to configure the Azure AD provisioning
95
95
96
96
9. Review the user attributes that are synchronized from Azure AD to PureCloud by Genesys in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the user accounts in PureCloud by Genesys 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 PureCloud by Genesys API supports filtering users based on that attribute. Select the **Save** button to commit any changes.
10. Under the **Mappings** section, select **Synchronize Azure Active Directory Groups to PureCloud by Genesys**.
113
122
114
123
11. Review the group attributes that are synchronized from Azure AD to PureCloud by Genesys in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the groups in PureCloud by Genesys for update operations. Select the **Save** button to commit any changes. PureCloud by Genesys does not support group creation or deletion and only supports updating of groups.
115
124
116
-
|Attribute|Type|
117
-
|---|---|
118
-
|displayName|String|
125
+
|Attribute|Type|Supported for filtering|
126
+
|---|---|---|
127
+
|displayName|String|✓|
119
128
|externalId|String|
120
129
|members|Reference|
121
130
@@ -144,9 +153,10 @@ Once you've configured provisioning, use the following resources to monitor your
144
153
145
154
## Change log
146
155
147
-
09/10 - Added support for enterprise attribute "employeeNumber".
156
+
* 09/10/2020 - Added support for extension enterprise attribute **employeeNumber**.
157
+
* 05/18/2021 - Added support for core attributes **phoneNumbers[type eq "work2"]**, **phoneNumbers[type eq "work3"]**, **phoneNumbers[type eq "work4"]**, **phoneNumbers[type eq "home"]**, **phoneNumbers[type eq "microsoftteams"]** and roles. And also added support for custom extension attributes **urn:ietf:params:scim:schemas:extension:genesys:purecloud:2.0:User:externalIds[authority eq ‘microsoftteams’]**, **urn:ietf:params:scim:schemas:extension:genesys:purecloud:2.0:User:externalIds[authority eq ‘zoomphone]** and **urn:ietf:params:scim:schemas:extension:genesys:purecloud:2.0:User:externalIds[authority eq ‘ringcentral’]**.
148
158
149
-
## Additional resources
159
+
## More resources
150
160
151
161
*[Managing user account provisioning for Enterprise Apps](../app-provisioning/configure-automatic-user-provisioning-portal.md)
152
162
*[What is application access and single sign-on with Azure Active Directory?](../manage-apps/what-is-single-sign-on.md)
Copy file name to clipboardExpand all lines: articles/aks/availability-zones.md
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,6 +54,12 @@ Volumes that use Azure managed disks are currently not zone-redundant resources.
54
54
55
55
Kubernetes is aware of Azure availability zones since version 1.12. You can deploy a PersistentVolumeClaim object referencing an Azure Managed Disk in a multi-zone AKS cluster and [Kubernetes will take care of scheduling](https://kubernetes.io/docs/setup/best-practices/multiple-zones/#storage-access-for-zones) any pod that claims this PVC in the correct availability zone.
56
56
57
+
### Azure Resource Manager templates and availability zones
58
+
59
+
When *creating* an AKS cluster, if you explicitly define a [null value in a template][arm-template-null] with syntax such as `"availabilityZones": null`, the Resource Manager template treats the property as if it doesn't exist, which means your cluster won’t have availability zones enabled. Also, if you create a cluster with a Resource Manager template that omits the availability zones property, availability zones are disabled.
60
+
61
+
You can't update settings for availability zones on an existing cluster, so the behavior is different when updating am AKS cluster with Resource Manager templates. If you explicitly set a null value in your template for availability zones and *update* your cluster, there are no changes made to your cluster for availability zones. However, if you omit the availability zones property with syntax such as `"availabilityZones": []`, the deployment attempts to disable availability zones on your existing AKS cluster and **fails**.
62
+
57
63
## Overview of availability zones for AKS clusters
58
64
59
65
Availability zones are a high-availability offering that protects your applications and data from datacenter failures. Zones are unique physical locations within an Azure region. Each zone is made up of one or more datacenters equipped with independent power, cooling, and networking. To ensure resiliency, there's always more than one zone in all zone enabled regions. The physical separation of availability zones within a region protects applications and data from datacenter failures.
@@ -201,6 +207,7 @@ This article detailed how to create an AKS cluster that uses availability zones.
0 commit comments