User-account correlation for Azure

[SUMAIYA_BABU]

The OOTB Azure connector uses default account attribute mapping and does not have an account_attribute field to customize the account attributes from target to saviynt. 

Is there a way to use customized mapping to bring 'employeeid' into saviynt so that we can use it for user-account correlation? Or If possible, what other attributes available from the out of the box mapping are usually used for user-account correlation?

[rushikeshvartak]

You can use endpoint level correlation rule with any attribute. 
in our case cp11 store employee id

[SUMAIYA_BABU]

@rushikeshvartak But there is no employeeid in the out of the box mapping for Azure connector.

We are using Azure connector and not Azure AD connector.

[Amit_Malik]

Hi @SUMAIYA_BABU ,

we are on 24.2 that still got account attribute field.

Try updating "Connection Attributes as Comma Separated", in connection type list in LOWER env after taking back up of original value

CLIENT_ID,CLIENT_SECRET,ACCESS_TOKEN,AAD_TENANT_ID,AZURE_MGMT_ACCESS_TOKEN,AUTHENTICATION_ENDPOINT,MICROSOFT_GRAPH_ENDPOINT,AZURE_MANAGEMENT_ENDPOINT,ImportUserJSON,CREATEUSERS,WINDOWS_CONNECTOR_JSON,CREATE_NEW_ENDPOINTS,ACCOUNT_ATTRIBUTES,ENTITLEMENT_ATTRIBUTE,DELTATOKENSJSON,ACCOUNT_IMPORT_FIELDS,CreateAccountJSON,UpdateAccountJSON,EnableAccountJSON,DisableAccountJSON,AddAccessJSON,RemoveAccessJSON,UpdateUserJSON,ChangePassJSON,RemoveAccountJSON,ConnectionJSON,CreateGroupJSON,UpdateGroupJSON,DeleteGroupJSON,ENTITLEMENT_FILTER_JSON,CreateTeamJSON,CreateChannelJSON,STATUS_THRESHOLD_CONFIG,ACCOUNTS_FILTER,PAM_CONFIG,ENDPOINTS_FILTER,ConfigJSON,MODIFYUSERDATAJSON

Thanks,

Amit

[SUMAIYA_BABU]

Hi @Amit_Malik We did the same thing for now. But the issue here is that everytime there is an upgrade, this is removed from all the connections and we have to reconfigure this. We have multiple Azure connectors and hence maintaining this configuration is difficult.

[rushikeshvartak]

You can raise enhancement to get it included in upcoming release