Skip to main content
All CollectionsMicrosoft Entra ID
Microsoft Entra ID data that Druva protects
Microsoft Entra ID data that Druva protects

This article provides the list of attributes of each Microsoft Entra ID entity that Druva protects.

Updated this week

Here’s the detailed information on each Microsoft Entra ID entity and its attributes that Druva protects.

Entity

Attributes

  • Tenant

  • Name

  • Tenant ID

  • Primary domain

  • Workload license

  • Country or region

  • Data location

  • Notification language

  • Technical contact

  • Global privacy contact

  • Privacy statement URL

  • Access management for Azure resources settings

  • Other tenant information

  • Company branding

  • Language

  • Sign-In background Image

  • Banner logo

  • User sign-in hint

  • Sign-in page text

  • Sign-in page background color

  • Square logo image

  • Square logo dark theme

  • User

  • Display name

  • First name ==> givenName

  • Last name ==> surname

  • User principal name

  • Object ID

  • User type

  • Creation type

  • Created date time

  • Last password change date time

  • External user state

  • External user state change date time

  • Sign in sessions valid from date time

  • Job title

  • Company name

  • Department

  • Employee ID

  • Employee type

  • Employee hire date

  • Office location

  • Manager

  • Street address

  • City

  • State or province

  • ZIP or postal code

  • Country or region

  • Business phone

  • Mobile phone

  • Email

  • Other emails

  • Fax number

  • Mail nickname

  • Age group

  • Consent provided for minor

  • Legal age group classification

  • Account enabled

  • Usage location

  • Preferred data location

  • On-premises immutable ID

  • On-premises security identifier

  • Extended columns

  • User setting

(User features, external collaboration settings)

  • Users can register applications

  • Restrict non-admin users from creating tenants

  • Users can create security groups

  • Guest user access restrictions

  • Restrict access to Azure AD administration portal

  • Allow users to connect their work or school account with LinkedIn

  • Show "keep user signed in"

  • Users can use preview features for My Apps

  • Administrators can access My Staff

  • Group

  • Name

  • Object ID

  • Group type

  • Membership type

  • Email

  • Source

  • Created at

  • Members

  • Owners

  • Deleted date-time

  • Description

  • Aliases

  • Privacy

  • Sensitivity label

  • Site address

  • Storage limit

  • MailEnabled

  • membershipRule

  • membershipRule

  • ProcessingState

  • preferredDataLocation

  • preferredLanguage

  • resourceBehaviorOptions

  • resourceProvisioningOptions

  • securityEnabled

  • securityIdentifier

  • theme

  • visibility

  • isAssignableToRole

  • Group setting

  • Self service group management

  • Security groups

  • Microsoft 365 groups

  • Roles and admins

  • Name

  • Description

  • isBuiltIn

  • isEnabled

  • rolePermissions

  • templateId

  • version

  • visibility

  • Enterprise applications

  • Name

  • Object ID

  • Application ID

  • Homepage URL

  • Created On

  • Properties - (Terms of Service URL, Privacy Statement URL, Reply URL, Assignment required, Visible to Others) ==> (replyUrls, info, loginUrl, logoutUrl)

  • Owners - (Name, Role assigned) ==> (using /owners endpoint)

  • Users and Groups

  • Certification expiry

  • Provisioning

  • Self-service

  • Single Sign-On

  • Roles and administrators

  • Security - Conditional Access

  • Security - Token Encryption

  • Security - Permissions

  • Applications

  • Name

  • Application ID

  • Created On

  • Certificates and Secrets

  • Object ID

  • Directory ID

  • Application ID URL

  • Supported Account Types

  • Client credentials

  • Redirection URLs

  • Licenses

  • Users may attach devices with Azure AD

  • Users may register their devices with Azure AD

  • Require multi-factor authentication to register or attach devices with Azure AD

  • Maximum number of devices per user

  • Enable Azure AD LAPS

  • Restrict users from recovering BitLocker keys for their owned devices

  • Device

  • Name

  • Enabled

  • OD

  • Version

  • Join Type

  • Owner

  • MDM

  • Compliant

  • Registered

  • Activity

  • Device setting

  • Users may attach devices with Azure AD

  • Users may register their devices with Azure AD

  • Require multi-factor authentication to register or attach devices with Azure AD

  • Maximum number of devices per user

  • Enable Azure AD LAPS

  • Restrict users from recover BitLocker keys of their owned devices

  • Domains

  • Name

  • Status

  • Federated

  • Primary

Did this answer your question?