Hello Ajay Neethikannan,
Thank you for posting your query in Microsoft Q&A.
As you are testing few scenarios to understand the user of different credentials such as Client Secrets and Client Certificates.
Case 1:
In some cases, the lastSignInRequestId is set to the value "aggregated", instead of showing the last sign-in requestId.
Last signIn request Id is showing as "aggregated" instead of showing the Id.
It might happen when you search for non-interactive sign-ins.
On this I request you to download the sign-in logs, the data won't be aggregated and will show the Date/Time (UTC) entries individually.
To make it easier to digest the data, non-interactive sign-in events are grouped. Clients often create many non-interactive sign-ins on behalf of the same user in a short time period. The non-interactive sign-ins share the same characteristics except for the time the sign-in was attempted. For example, a client may get an access token once per hour on behalf of a user. If the state of the user or client doesn't change, the IP address, resource, and all other information is the same for each access token request. The only state that does change is the date and time of the sign-in. When Azure AD logs multiple sign-ins that are identical other than time and date, those sign-ins are from the same entity and are aggregated into a single row. A row with multiple identical sign-ins (except for date and time issued) have a value greater than 1 in the # sign-ins column. These aggregated sign-ins may also appear to have the same time stamps. The Time aggregate filter can set to 1 hour, 6 hours, or 24 hours. You can expand the row to see all the different sign-ins and their different time stamps.
I suggest you refer the below document.
https://learn.microsoft.com/en-us/entra/identity/monitoring-health/concept-noninteractive-sign-ins
Disabling the data aggregation within the Sign-in logs isn't possible, I suggest you provide your feedback so that our engineering team can look into this as a feature request
Case 2:
Delays in getting the appCredentialSignInActivity for some applications.
Two applications using App Credential (Client Secret) to get data using MS Graph. For Application one we see interactive sign-in and for Application two it is non-interactive sign-in.
Here we are not able to see all non-interactive sign-ins. A Non-interactive sign-in can only be used after a successful interactive sign-in happens. During noninteractive authentication, the user does not input logon data, instead, previously established credentials are used.
Non-interactive sign-in events are grouped. Clients often create many non-interactive sign-ins on behalf of the same user in a short time period.
If you observe in the second screenshot in non-interactive sign-in logs, it shows he sign-in logs as graph is accessing two different resources, but not on a single resource.
Case 3:
Sign-in activity for application credential is represented using the SignInActivity, but the API response is showing only the lastSignInDateTime and lastSignInRequestId.
Again, Sign-ins are aggregated in the non-interactive users when the following data matches:
Application
User
IP address
Status
Resource ID
I suggest you refer the below document.
Case 4 :
Absence of data, could this be associated with licensing.
As you mentioned there are no appCredentialSignInActivities associated with this application and is on free tenant, you might not see the api activity in that tenant.
I suggest referring below documentation for graph permissions on a multi-tenant application
https://learn.microsoft.com/en-us/entra/identity-platform/v2-admin-consent
https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/grant-admin-consent?pivots=portal
Please let me know if you have further queries on this.