Documentation
Entra Policy Suite settings
Every setting in Entra Policy Suite 2.0.107: what it does, what happens when it is on or off, the risk and how to reverse it, what it requires, and the default and recommended value.
52 settings · documented for Entra Policy Suite 2.0.107 · Security review pack· Scripts· Error codes
Settings > General
- Environment name Platform.EnvironmentName
A short name for this install, shown in the header of every page and in the subject of every alert mail, so people can tell production from test at a glance. When this install reports to Invardia, the name Invardia ke...
- Tenant name Platform.TenantName
The tenant's name as people know it, shown in the page header next to the tenant id and in alert mails.
- Time zone for schedules Platform.TimeZone
The time zone the job schedules are read in: 'daily 01:00' means 01:00 in this time zone, summer time included. The pages always show times in your browser's local time, whatever this is set to.
- Ask for a note on every action Platform.AskForNote
Whether the web app asks for a note (kept in the audit trail) before it sends an action. The action, who did it and when are always in the audit trail; the note is the only optional part.
Settings > User tagging
- User tagging UserTagging.Enabled
Switches the user tagging feature on: the job that evaluates the user rules and gives every user their tags (persona, classification, authentication ...) in extension attributes.
- User tagging mode (scheduled runs) UserTagging.Mode
What a SCHEDULED user tagging run does. A Run now request from the Jobs page says its own mode.
- Also tag a user at once when it changes UserTagging.RunOnDirectoryChange
Besides the schedule, tag a NEW or CHANGED user within about 5 minutes: only the users whose rule properties changed (a Graph delta of exactly those properties), not everyone.
- Never tag these users UserTagging.ExcludeObjects
Users that the tagging job never touches - e.g. a directory sync service account. They are left out before the plan is made.
Settings > Device tagging
- Device tagging DeviceTagging.Enabled
Switches the device tagging feature on: the job that evaluates the device rules and writes each device's tags to its extension attributes in Entra ID.
- Device tagging mode (scheduled runs) DeviceTagging.Mode
What a SCHEDULED device tagging run does. A Run now request says its own mode.
- Also tag a device at once when it changes DeviceTagging.RunOnDirectoryChange
Besides the schedule, tag a NEW or CHANGED device within about 5 minutes: only the devices whose rule properties changed (a Graph delta of exactly those properties), not every device.
- Never tag these devices DeviceTagging.ExcludeObjects
Devices that the tagging job never touches - e.g. a directory sync service account. They are left out before the plan is made.
Settings > Tamper monitor
- Restore foreign changes automatically TamperMonitor.AutoRestore
Whether the monitor puts the engine's value back by itself after every foreign change it finds, instead of waiting for an admin to choose Accept or Restore.
Settings > CA Policy Analyzer
- CA Policy Analyzer CAPolicyAnalyzer.Enabled
Switches the CA Policy Analyzer on: it reads your Conditional Access policies and the sign-in logs and shows, per user, who a policy blocked or challenged and why - the check before you move a policy to pilot or produ...
Settings > Conditional Access
- Group targeting method CA.GroupTargetingMethod
How the Conditional Access policies target groups (v1: Dynamic_Using_Tags, Manual_Assignment_Advanced or Manual_Assignment_Simple), imported from the v1 configuration. The Conditional Access page uses it to know which...
- Authentication strength name (FIDO2) CA.AuthStrengthFidoName
The name of the authentication strength that requires FIDO2, imported from the v1 configuration. The Conditional Access page expects it in the templates that require FIDO2.
- Authentication strength name (Windows Hello) CA.AuthStrengthWhfbName
The name of the authentication strength that requires Windows Hello for Business, imported from the v1 configuration. The Conditional Access page expects it in the templates that require it.
- Named location for denied countries CA.DeniedCountriesLocationName
The name of the named location that lists the countries sign-ins are blocked from, imported from the v1 configuration. The Conditional Access page expects it in the template that blocks those countries.
Settings > Named locations
- Keep the Azure service tags as named locations NamedLocations.Enabled
Switches the daily named-locations job on (v1's EntraNamedLocations_AzureNetworkServiceTags.ps1): for each service tag in the list (v1's CSV, imported on the Import v1 page) it reads the tag's IP prefixes and keeps th...
- Azure region for the service-tag named locations NamedLocations.Region
The Azure region whose service tags become named locations (v1 used westeurope, hard-coded). Set by the v1 import.
Settings > Identity report
- Identity report IdentityReport.Enabled
Switches the identity report on: a daily snapshot of every user and device - MFA, sign-in, licenses, AD, devices - shown on the Identity page as gap views with filters and pivots. Read only: nothing in the tenant or A...
- Snapshots to keep IdentityReport.KeepRuns
How many report snapshots the database keeps (the newest ones). The Identity page can show any kept snapshot and how the gap counts changed.
- Mail the workbook after each run IdentityReport.MailWorkbook
Sends the report as an Excel workbook (v1's sheets plus the gap views) after every run, with the open High / Medium gaps in the mail - to 'Who gets the workbook', or the alert recipients when that is empty.
- Who gets the workbook IdentityReport.MailRecipients
The addresses the identity report workbook goes to (v1: $global:Mail_Identity_Maintenance_TO), e.g. the identity team rather than the security alert list.
- Device counts: devices synced in the last N days IdentityReport.DeviceCountWindowDays
The per-user device counts (iPhone / iPad / Android / Windows, company / personal) and the smartphone flags only count Intune devices that synced in this many days. The Devices list always shows every device.
- Inactive after N days IdentityReport.InactiveDays
The view "No sign-in for 90 days": enabled users of the active classifications with no cloud and no AD sign-in in this many days.
- Long inactive after N days IdentityReport.LongInactiveDays
The view "No sign-in for a year": the same as the inactive view, with this longer window.
- Guests inactive after N days IdentityReport.GuestInactiveDays
The view "Guests without a recent sign-in": enabled guests with no cloud sign-in in this many days.
- New hires: grace period (days) IdentityReport.NewHireGraceDays
The view "Active without MFA" leaves out users whose hire date (the hire date attribute) is more than this many days in the future - they have not started yet. A user without a valid hire date is always shown.
- Hire date attribute IdentityReport.HireDateAttribute
The extension attribute that holds a user's hire (start) date, read by the "Active without MFA" view.
- AD validation: user OU pattern IdentityReport.AdOu.User
Which AD location is right for an AD-synced user (views 'AD users in the right / wrong OU' and the shared device user views). A regular expression matched against the user's on-premises distinguished name (e.g. OU=Use...
- AD validation: service account OU pattern IdentityReport.AdOu.ServiceAccount
Which AD location is right for an AD-synced service account. A regular expression matched against the user's on-premises distinguished name (e.g. OU=Users,OU=Corp). Empty: nobody is validated by this rule.
- AD validation: shared user OU pattern IdentityReport.AdOu.SharedUser
Which AD location is right for a shared user (a column of the user list). A regular expression matched against the user's on-premises distinguished name (e.g. OU=Users,OU=Corp). Empty: nobody is validated by this rule.
- AD validation: shared mailbox OU pattern IdentityReport.AdOu.SharedMailbox
Which AD location is right for a shared mailbox account (a column of the user list). A regular expression matched against the user's on-premises distinguished name (e.g. OU=Users,OU=Corp). Empty: nobody is validated b...
- Leave these users out of the report IdentityReport.ExcludeObjects
Users the report never lists, by UPN or display name (wildcards allowed). v1 left out the directory synchronization account.
Settings > Pro: passkey rollout
- The identity report column that names the persona ProPasskey.PersonaColumn
Pro. The passkey rollout groups the users by this column of the identity report - one of your tag columns (the classification tag by default).
- Mail each persona owner who is not ready yet ProPasskey.DigestEnabled
Pro. After the identity report runs, each persona that has an owner (set on the passkey rollout page) gets at most one mail a day: how many are ready, the target date, and the people who still need a passkey or anothe...
Settings > Pro: stale identities
- Inactive after (days without a sign-in) ProStale.InactiveDays
Pro. A user or guest whose last sign-in (interactive, non-interactive or on-premises) is older than this many days is on the stale identities list for review.
- Never signed in, created more than (days) ago ProStale.NeverSignedInDays
Pro. An account that has never signed in and was created more than this many days ago is on the stale identities list for review.
Settings > Hybrid worker
- A worker is late after (minutes) HybridWorker.StaleMinutes
The hybrid worker reports every 5 minutes. When a worker has not reported for this many minutes, Administration > Hybrid worker and the Overview show it as late, with how long ago it last reported.
- AD environments (one worker each) HybridWorker.EnvironmentByUpnSuffix
For several Active Directory forests or domains (v1 ran its scripts once per environment: Internal_Prod, DMZ_Prod, Internal_Dev, Internal_Test). Each line sends the AD changes of users whose on-premises user principal...
Settings > Logging
- Log level: user tagging Log.Level.UserTagging
How much the run log of user tagging keeps (v1: each script's Verbose / Debug switch).
- Log level: device tagging Log.Level.DeviceTagging
How much the run log of device tagging keeps (v1: each script's Verbose / Debug switch).
- Log level: the identity report Log.Level.IdentityReport
How much the run log of the identity report keeps (v1: each script's Verbose / Debug switch).
- Log level: the CA Policy Analyzer Log.Level.CAPolicyAnalyzer
How much the run log of the CA Policy Analyzer keeps (v1: each script's Verbose / Debug switch).
- Log level: the named locations job Log.Level.NamedLocations
How much the run log of the named locations job keeps (v1: each script's Verbose / Debug switch).
- Log level: the Invardia telemetry Log.Level.Uplink
How much the run log of the Invardia telemetry keeps (v1: each script's Verbose / Debug switch).
- Log level: the update job Log.Level.Update
How much the run log of the update job keeps (v1: each script's Verbose / Debug switch).
- Log level: the backup job Log.Level.Backup
How much the run log of the backup job keeps (v1: each script's Verbose / Debug switch).
- Keep run logs (days) Log.KeepDays
How long the lines of every run log are kept. The run records (what ran, when, its counts) and the audit trail are not removed.
Settings > Conditional Access options from Graph
- Read the policy options from Microsoft Graph every month CaOptions.Enabled
Once a month the CaOptions job reads Microsoft Graph: the values every Conditional Access field allows (Graph v1.0's published schema) and your tenant's authentication strengths, named locations, terms of use and dire...
Settings > Pro: license optimization
- A license counts as unused after this many days without a sign-in ProLicenseOpt.UnusedDays
Pro, license optimization: a license on a user with no sign-in (cloud, non-interactive or AD) in this many days - or none ever - is listed as unused and priced as a saving. A license on a disabled account is always li...
No setting matches.