users

•Id

•UserPrincipalName

•GivenName

•OnPremisesUserPrincipalName

•Surname

•Mail

•DisplayName

•DeletedDateTime

•UserType

•Country

•Department

•OfficeLocation

•UsageLocation

•AccountEnabled

•LastSignIn

•CountryLat

•CountryLng

•Guid

•String

•String

•String

•String

•String

•String

•DateTime

•String

•String

•String

•String

•String

•Boolean

•DateTime

•Double

•Double

user_skus

•UserId

•SkuId

•Guid

•Guid

user_services

•Service

•CapabilityStatus

•AssignedDateTime

•UserId

•ServicePlanId

•String

•String

•DateTime

•Guid

•Guid

skus

•Id

•SkuId

•SkuPartNumber

•DisplayName

•AppliesTo

•CapabilityStatus

•ConsumedUnits

•String

•Guid

•String

•String

•String

•String

•String

service_plans

•Id

•Name

•ProvisioningStatus

•AppliesTo

•DisplayName

•Guid

•String

•String

•String

•String

sku_service_plans

•SkuId

•ServicePlanId

•Guid

•Guid

sign_ins_azure

(fetch_from = AD)

•Id

•UserId

•AppId

•AppDisplayName

•CreatedDateTime

•UserPrincipalName

•IpAddress

•LocationCountryOrRegion

•LocationState

•LocationCity

•LocationGeoCoordinatesLatitude

•LocationGeoCoordinatesLongitude

•Guid

•Guid

•Guid

•String

•DateTime

•String

•String

•String

•String

•String

•Double

•Double

sign_ins_dynamics

(fetch_from = CRM)

•Id

•UserId

•UserPrincipalName

•CreatedOn

•Guid

•Guid

•String

•DateTime

Be aware:

The sign_ins_azure table is only generated when the Fetch Additional Data parameter is set to AD. The sign_ins_dynamics table is only generated when the Fetch Additional Data parameter is set to CRM. When set to None, neither sign-in table is created.