All members of group is not syncing from Azure AD

Hi PrakashRIndia,

Appreciate your patience.
I believe you have submitted a ticket with our Support team by now.

Noted you mentioned: "...almost 100 users who are present in the group at Azure AD but same are not reflecting in CMA due to which I am unable to provide access to SDP client. Pls suggest what to do?" 

There are a few possibilities users are not sync'ed from Azure AD (Entra) to CMA, such as (and not limited to the following):
a- missing details/fields (like last name not present...)
b- user not included in target AD group (users mis-grouped...)...

Here are 2 points to consider for next actions:
1. Identify/List the current SDP/ZTNA users having issues connecting on Cato Client. 
2. Check on the related error logs for the users not synced from Azure AD. (hope the root cause can be identified on the logs)

Hope this helps 🙏
Thank you.

I am using SCIM to connect to Azure AD. I tried everything like doing Start/Stop provisioning in Azure AD for Cato Enterprise Application. I even did On demand provisioning but then also users are not syncing from Azure AD to CMA

Hey there!

Sounds like you've run into a frustrating issue. From what you're describing, it looks like the sync between CMA and Azure AD hasn't properly completed yet. Are you using SCIM or LDAP to connect to your Azure AD?

If you're using LDAP, By default, Cato starts the daily automatic LDAP sync for all accounts at 12:00 am UTC and it can take several hours to actually complete the full sync process.  You can trigger a manual sync at any time by using the "Sync Now" feature in the Cato Management Application (CMA) - but it will still take a couple of hours to fully propogate

Hello,
Have you checked that the users not syncing have all the required attributes such as
Email, User Principal Name (UPN), given name, and surname?
Are you using a custom UPN other than the Azure default? 
If this is a migration from LDAP you may also want to check for conflicts.
Do the CMA event logs or audit and provisioning logs in the enterprise app shed any additional insight as to what the issue is? 
Use the "Provision on Demand" to force the sync of a problem user and then check these logs.