Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.

Azure AD - REST - Channel Membership

aalvarez_mk
New Contributor II
New Contributor II

We have a requirement to import channel memberships from Azure. We have been told the OOTB connector does NOT import channel membership.

We are building a REST connector to import the channel memberships. There are 2 questions we are facing.

1. Can the REST connector simply import the enttoacct portion of the ImportAccountEntJSON since we have all other data?

2. Can we reference the entitlementID and a custom property from the entitlement in the http url? I know we can do that in the add access JSON.

Example add access JSON snippet for add access:

"url": "https://graph.microsoft.com/v1.0/teams/${entitlementValue.customproprty4}/channels/${entitlementValu...",
We want to replicate that in enttoacct. Documentation only references using ${id} variable to access the entitlement value, which seems like it is not supported.

3 REPLIES 3

rushikeshvartak
All-Star
All-Star

1. Importing Only the enttoacct Portion of ImportAccountEntJSON using REST Connector

Do you mean importing data in existing endpoint ?

2. Referencing entitlementID and Custom Properties in HTTP URL

Yes, you can reference custom properties from the entitlement in the HTTP URL when using a REST connector. While the documentation might primarily reference the use of the ${id} variable, you can indeed use other variables such as ${entitlementValue.customproperty4}.


Regards,
Rushikesh Vartak
If you find this response useful, kindly consider selecting 'Accept As Solution' and clicking on the 'Kudos' button.

1. Importing Only the enttoacct Portion of ImportAccountEntJSON using REST Connector

Yes, importing data in an existing endpoint (populated from OOTB Azure connector

2. Referencing entitlementID and Custom Properties in HTTP URL

Will test this functionality. Can you confirm it is available in the ImportAccountEntJSON and specifically in acctEntParams?

1 . You need to use different endpoints

2. Does it coming from APi response or this are saviynt attributes. If saviynt use saviynt api

Refer Saviynt API Documentation https://docs.saviyntcloud.com/bundle/API-Reference-Guide/page/Content/API-References.htm


Regards,
Rushikesh Vartak
If you find this response useful, kindly consider selecting 'Accept As Solution' and clicking on the 'Kudos' button.