TestConnection-AzureAD executing ATTESTATIONCREATEJOB,DashboardRefreshJob,EnterpriseRoleManage jobs

[sreehariv]

Hello Team,

We have observed the following and would like to know why and how the following behavior occures upon doing a test connection for Azure AD.

We have Azure AD Connector configured and when we did the test connection, a popup  displayed saying the below:

Connection to Azure AD Successful
Do you wish to import your Azure AD objects data?
Please note this could take few seconds to several minutes, depending on the size of your Azure AD account.
After clicking the 'Yes' button, go to 'Job Control Panel' in the Admin module to see the progress of your data import.                                            - Yes and No options

and when we click "No" it is saved and shows 4 jobs are executing.

Recently we have observed this in prod environment also. there we are not sure whether they did a test connection or not but they mentioned the following jobs are automatically created and triggered.

SAVIYNTATTESTATION-global::azuread::xxxxx::azure_ad

SAVIYNTDASHBOARDS-global::azuread::xxxxxx::azure_ad

SAVIYNTFIREFIGHTER-global::azuread::xxxxxx::azure_ad

SAVIYNTWSRETRY-global::azuread::xxxxxx::azure_ad UTILITY Provisioning Job (WSRETRYJOB)

The same thing happened in DEV environment and we can see the same job names in dev and when i did the test connection with no option the jobs timestamp got updated.

could you please let us know what is the trigger that is causing to trigger these jobs.

the above jobs are of type below:

SAVIYNTATTESTATION-global::azuread::xxxxx::azure_ad	ATTESTATION	Create or Schedule Attestation (ATTESTATIONCREATEJOB)
SAVIYNTDASHBOARDS-global::azuread::xxxxxx::azure_ad	UTILITY	Dashboard Refresh Job (DashboardRefreshJob)
SAVIYNTFIREFIGHTER-global::azuread::xxxxxx::azure_ad	UTILITY	Create Tasks for Future Ent Role Requests (EnterpriseRoleManagementJob)
SAVIYNTWSRETRY-global::azuread::xxxxxx::azure_ad	UTILITY	Provisioning Job (WSRETRYJOB)

Thanks

Sreehari

[This post has been edited by a Moderator to merge two posts together.]

[RakeshMG]

These jobs are created when the Azure Ad test connection was checked.  When you check the test connection for Azure Ad, there will be a popup displayed as shown below

Connection to Azure AD Successful
Do you wish to import your Azure AD objects data?
Please note this could take few seconds to several minutes, depending on the size of your Azure AD account.
After clicking the 'Yes' button, go to 'Job Control Panel' in the Admin module to see the progress of your data import.                                           

- Yes and No options

If you click on Yes, then the following jobs are being created in the backend.

Job Details:

• SAVIYNTATTESTATION-global::azuread::Connectionname::azure_ad (ATTESTATIONCREATEJOB) – Use this job to create or schedule attestation. The job trigger is automatically created when an attestation is scheduled. So this will have impact on attestation if there is anything scheduled for azure ad otherwise No impact

• SAVIYNTDASHBOARDS-global::azuread::Connectionname::azure_ad (Dashboard Refresh Job ) – this will be refreshing of tile values  visible on dashboards and it is not going to do anything with azure ad  - Hence No impact

• SAVIYNTFIREFIGHTER-global::azuread::Connectionname::azure_ad (EnterpriseRoleManagementJob)  - this will affect the future dated entitlement requests (it will create tasks after the specified date and time in the request)  otherwise No impact

• SAVIYNTWSRETRY-global::azuread::Connectionname::azure_ad (Wsretry) – This will try to execute and complete the pending tasks for azure ad (both provisioning and deprovisioning)

If you click on No, then these are not getting created but sometimes, even if you select No, Saviynt executes these jobs in the backend if they are already created. This happens sometimes when we do the test connection for azure.

These jobs can be deleted and if auto sync after test connection is not required , kindly ensure to select “No option”.