Skip to main content

Naming Conventions

This document describes the emoji-based naming convention used throughout this documentation to ensure consistent, visual identification of resources.

Core Principles​

All resources follow this pattern:

[Type Icon][Target Icon][Modifiers] [Type Code] - [Descriptive Name]

Icon Reference​

Type Icons (Primary Category)​

IconMeaningUsed For
πŸ›‘οΈSecurity GroupEntra ID Security Groups
🚦Conditional AccessConditional Access Policies
βš™οΈConfigurationConfiguration Profiles
πŸ“Named LocationConditional Access Named Locations
πŸš€AutopilotAutopilot Deployment Profiles
πŸ“šComplianceCompliance Policies
πŸ“œScriptCompliance Scripts

Target Icons (Who/What is Affected)​

IconMeaningDescription
πŸ§‘β€πŸ’ΌUsersAffects user accounts
πŸ‘¨β€πŸ’ΌAdmin/UserAlternative user icon
πŸ’»Devices (Desktop)Desktop/laptop devices
πŸ“±Mobile DevicesPhones and tablets
πŸͺŸWindowsWindows-specific
🍏ApplemacOS or iOS
πŸ€–AndroidAndroid devices
🐧LinuxLinux devices

Modifier Icons (Behavior/Status)​

IconMeaningDescription
πŸ‘ˆManual AssignmentManually assigned membership (not dynamic)
⛓️Dynamic RuleDynamic group membership based on rules
πŸ”“Exception/AllowGrants access or creates exception
πŸ”Block/DenyBlocks access or enforces restriction
🚩GeographicLocation-based policies

Conditional Access Policy Status (CA Policies Only)​

IconMeaningCA Action
🟒Grant AccessPolicy grants access (with conditions like MFA, compliant device, etc.)
πŸ”΄Block AccessPolicy explicitly blocks access
🟠Warning/MediumMedium severity or special conditions

Named Location Trust Levels​

IconMeaningTrust Level
🟒TrustedTrusted/safe locations
πŸ”΄Non-TrustedHigh risk / blocked locations
🟠Less-TrustedMedium risk / caution locations

Type Codes (Text Abbreviations)​

CodeFull NameUsed For
GroupSecurity GroupEntra ID Security Groups
CAConditional AccessConditional Access Policies
CPConfiguration ProfileIntune Configuration Profiles
NLOCNamed LocationCA Named Locations
DPDeployment ProfileAutopilot Deployment Profiles
ComplianceCompliance PolicyIntune Compliance Policies
CCScriptCompliance Custom ScriptCustom compliance detection scripts

Examples by Category​

Security Groups​

User Groups - Exception Groups​

πŸ›‘οΈπŸ§‘β€πŸ’ΌπŸ‘ˆπŸ”“πŸš¦Group - No compliant device required for πŸ’»πŸͺŸ users
  • πŸ›‘οΈ = Security Group
  • πŸ§‘β€πŸ’Ό = Users
  • πŸ‘ˆ = Manual assignment
  • πŸ”“ = Exception (allows something)
  • 🚦 = Related to Conditional Access
  • πŸ’»πŸͺŸ = Windows desktop devices

User Groups - Restriction Groups​

πŸ›‘οΈπŸ§‘β€πŸ’ΌπŸ‘ˆπŸ”πŸš¦Group - Not Allowed to Work Remote Users
  • πŸ›‘οΈ = Security Group
  • πŸ§‘β€πŸ’Ό = Users
  • πŸ‘ˆ = Manual assignment
  • πŸ” = Block/restriction
  • 🚦 = Related to Conditional Access

Device Groups - Dynamic Assignment​

πŸ›‘οΈπŸͺŸπŸ’»β›“️Group - Autopilot Devices
  • πŸ›‘οΈ = Security Group
  • πŸͺŸ = Windows
  • πŸ’» = Devices
  • ⛓️ = Dynamic membership rule

Device Groups - Manual Assignment with Exception​

πŸ›‘οΈπŸͺŸπŸ’»πŸ‘ˆπŸ”“βš™οΈGroup - Screen Lock Timer Disabled
  • πŸ›‘οΈ = Security Group
  • πŸͺŸ = Windows
  • πŸ’» = Devices
  • πŸ‘ˆ = Manual assignment
  • πŸ”“ = Exception (disables a security control)
  • βš™οΈ = Related to configuration policy

Special Groups​

πŸ›‘οΈπŸ§‘β€πŸ’Όβ›“οΈπŸ”“πŸš¦Group - Break the Glass solution
  • πŸ›‘οΈ = Security Group
  • πŸ§‘β€πŸ’Ό = Users
  • ⛓️ = Dynamic membership
  • πŸ”“ = Exception (emergency access)
  • 🚦 = Related to Conditional Access

Conditional Access Policies​

Grant Access Policies (Green - 🟒)​

πŸš¦πŸŸ’πŸ‘¨β€πŸ’ΌCA - MFA for All Users
  • 🚦 = Conditional Access
  • 🟒 = Grant access (with MFA requirement)
  • πŸ‘¨β€πŸ’Ό = Users
πŸš¦πŸŸ’πŸ’»CA - Require Compliant Device πŸͺŸ
  • 🚦 = Conditional Access
  • 🟒 = Grant access (requires compliant device)
  • πŸ’» = Devices
  • πŸͺŸ = Windows-specific

Block Access Policies (Red - πŸ”΄)​

πŸš¦πŸ”΄πŸ“œCA - Block Legacy Other Clients
  • 🚦 = Conditional Access
  • πŸ”΄ = Block access
  • πŸ“œ = Related to legacy protocols/scripts
πŸš¦πŸ”΄πŸ‘¨β€πŸ’ΌCA - Block External login for BTG
  • 🚦 = Conditional Access
  • πŸ”΄ = Block access
  • πŸ‘¨β€πŸ’Ό = Users (admin/Break the Glass)

Geographic Policies​

πŸš¦πŸ”΄πŸš©CA - Block Non-Trusted Countries All Cloud Apps
  • 🚦 = Conditional Access
  • πŸ”΄ = Block access
  • 🚩 = Geographic/location-based
🚦🟠🚩CA - Require Compliant Device in Less-Trusted Countries
  • 🚦 = Conditional Access
  • 🟠 = Medium severity (grant with extra conditions)
  • 🚩 = Geographic/location-based

Mobile Policies​

πŸš¦πŸŸ’πŸ“±CA - Require MAM AppProPol or Compliant Device 🍏
  • 🚦 = Conditional Access
  • 🟒 = Grant access (with MAM or compliance requirement)
  • πŸ“± = Mobile devices
  • 🍏 = iOS/macOS specific

Named Locations​

Trusted Locations (Green)​

πŸ“πŸŸ’NLOC - Panic Room
πŸ“πŸŸ’NLOC - Customer Locations
  • πŸ“ = Named Location
  • 🟒 = Trusted/safe

Non-Trusted Locations (Red/Orange)​

πŸš©πŸ”΄NLOC - Non-Trusted Countries
🚩🟠NLOC - Less-Trusted Countries
  • 🚩 = Geographic
  • πŸ”΄ = High risk / non-trusted
  • 🟠 = Medium risk / less-trusted

Configuration Profiles​

Windows Device Profiles​

βš™οΈπŸͺŸπŸ’»CP - Screen Lock Timer
  • βš™οΈ = Configuration
  • πŸͺŸ = Windows
  • πŸ’» = Devices

Windows Device Profiles with Exception​

βš™οΈπŸͺŸπŸ’»πŸ”“CP - Screen Lock Timer - Disable
  • βš™οΈ = Configuration
  • πŸͺŸ = Windows
  • πŸ’» = Devices
  • πŸ”“ = Exception (disables control)

Windows User Profiles - Block​

βš™οΈπŸͺŸπŸ§‘β€πŸ’ΌCP - OneDrive - Block personal OneDrive
  • βš™οΈ = Configuration
  • πŸͺŸ = Windows
  • πŸ§‘β€πŸ’Ό = Users

Windows User Profiles - Allow​

βš™οΈπŸͺŸπŸ§‘β€πŸ’ΌπŸ”“CP - OneDrive - Allow personal OneDrive
  • βš™οΈ = Configuration
  • πŸͺŸ = Windows
  • πŸ§‘β€πŸ’Ό = Users
  • πŸ”“ = Exception (allows something)

Autopilot Deployment Profiles​

πŸš€Autopilot DP - User Driven
πŸš€Autopilot DP - Self Deploy
πŸš€Autopilot DP - User Driven with Local Admin
  • πŸš€ = Autopilot deployment profile

Compliance Policies​

Windows Compliance​

πŸ“šπŸͺŸπŸ’»Compliance - Windows - Bitlocker
πŸ“šπŸͺŸπŸ’»Compliance - Windows - Secure Boot
  • πŸ“š = Compliance policy
  • πŸͺŸ = Windows
  • πŸ’» = Devices

Custom Compliance Scripts​

πŸ“šπŸͺŸπŸ’»πŸ“œCCScript - Windows - Detect RMM
  • πŸ“š = Compliance
  • πŸͺŸ = Windows
  • πŸ’» = Devices
  • πŸ“œ = Script

Quick Reference Table​

Common Combinations​

IconsMeaningExample
πŸ›‘οΈπŸ§‘β€πŸ’ΌπŸ‘ˆπŸ”“πŸš¦User group, manual, exception for CAException from MFA requirement
πŸ›‘οΈπŸ§‘β€πŸ’ΌπŸ‘ˆπŸ”“βš™οΈUser group, manual, exception for configException from OneDrive restriction
πŸ›‘οΈπŸ§‘β€πŸ’ΌπŸ‘ˆπŸ”πŸš¦User group, manual, block for CABlocked from remote work
πŸ›‘οΈπŸͺŸπŸ’»β›“️Windows device group, dynamicAll autopilot devices
πŸ›‘οΈπŸͺŸπŸ’»πŸ‘ˆπŸ”“βš™οΈWindows device group, manual exceptionRDP enabled devices
πŸš¦πŸŸ’πŸ‘¨β€πŸ’ΌCA policy, grant access, for usersMFA requirements
πŸš¦πŸ”΄πŸ“œCA policy, block access, legacy protocolsBlock legacy auth
πŸš¦πŸ”΄πŸš©CA policy, block access, geographicBlock from countries
πŸš¦πŸŸ’πŸ’»CA policy, grant access, for devicesRequire compliant device
βš™οΈπŸͺŸπŸ’»Config profile, Windows, devicesStandard device config
βš™οΈπŸͺŸπŸ§‘β€πŸ’ΌπŸ”“Config profile, Windows, users, allowAllow exception for users

Understanding CA Policy Colors​

Important distinction for Conditional Access policies:

  • 🟒 Green = Grant Access (but with conditions)

    • Example: πŸš¦πŸŸ’πŸ‘¨β€πŸ’ΌCA - MFA for All Users
    • Meaning: Users are granted access, but they must perform MFA first
    • Still enforces security, but doesn't block completely
  • πŸ”΄ Red = Block Access (explicit deny)

    • Example: πŸš¦πŸ”΄πŸ“œCA - Block Legacy Other Clients
    • Meaning: Access is completely blocked, no way around it
  • 🟠 Orange = Grant with Extra Caution (medium severity)

    • Example: 🚦🟠🚩CA - Require Compliant Device in Less-Trusted Countries
    • Meaning: Access granted but with stricter requirements

Naming Best Practices​

  1. Always start with the type icon (πŸ›‘οΈ, 🚦, βš™οΈ, etc.)
  2. Add target icon to show what's affected (πŸ§‘β€πŸ’Ό, πŸ’», πŸ“±)
  3. Include modifiers to show behavior:
    • πŸ‘ˆ for manual assignment
    • ⛓️ for dynamic groups
    • πŸ”“ for exceptions/allows
    • πŸ” for blocks
    • πŸŸ’πŸ”΄πŸŸ  for CA policy actions (grant/block/caution)
  4. Add platform icons where relevant (πŸͺŸ, 🍏, πŸ€–, 🐧)
  5. Use the text code (Group, CA, CP, etc.)
  6. Write a clear descriptive name in English

Bad Examples βŒβ€‹

  • Group - Windows Devices (missing icons)
  • πŸ›‘οΈGroup - Autopilot (missing device type and assignment type)
  • CA - Block (not descriptive enough)

Good Examples βœ…β€‹

  • πŸ›‘οΈπŸͺŸπŸ’»β›“️Group - Autopilot Devices
  • πŸš¦πŸ”΄πŸš©CA - Block Non-Trusted Countries All Cloud Apps
  • πŸš¦πŸŸ’πŸ‘¨β€πŸ’ΌCA - MFA for All Users
  • βš™οΈπŸͺŸπŸ’»πŸ”“CP - Screen Lock Timer - Disable

Why This Convention?​

Visual Clarity​

The emoji icons allow you to instantly recognize what a resource is and does:

  • See 🟒 in CA? It grants access (with conditions)
  • See πŸ”΄ in CA? It blocks access completely
  • See πŸ”“? It's an exception
  • See πŸ”? It blocks something
  • See 🚩? It's location-based

Cross-Tenant Consistency​

When managing multiple tenants with SuperVision, consistent naming ensures:

  • Easy identification across environments
  • Predictable resource discovery
  • Simplified documentation
  • Better audit trails

Self-Documenting​

The name tells you:

  • What it is (Group, CA, CP)
  • Who/What it affects (users, devices, platform)
  • How it works (manual, dynamic, exception, block, grant)
  • Why it exists (descriptive name)

Remember: Good naming is not about being clever. It's about being instantly understandable to anyone who reads it β€” including your future self at 3 AM during an incident.


Platform-Specific Icons​

When a policy applies to a specific platform, add the platform icon at the end of the emoji sequence:

PlatformIconUsage
WindowsπŸͺŸCA - Require Compliant Device πŸͺŸ
macOS🍏CA - Require Compliant Device 🍏
iOS🍏CA - Require MAM AppProPol or Compliant Device 🍏
AndroidπŸ€–CA - Require MAM AppProPol or Compliant Device πŸ€–
Linux🐧CA - Require Compliant Device 🐧

This document is a living standard. As new patterns emerge, update this reference accordingly.