Introduction
One of the most overlooked aspects of Microsoft Intune administration is naming conventions. While naming standards may seem like a minor detail during the initial deployment, they become critical as the environment grows.
A well-structured naming convention improves visibility, simplifies administration, accelerates troubleshooting, and helps maintain consistency across teams.
This article outlines the naming standards I use to keep Intune environments organized and manageable.
Why Naming Conventions Matter
As organizations scale, Intune environments can quickly contain:
- Hundreds of applications
- Multiple compliance policies
- Configuration profiles
- Security baselines
- Device groups
- Administrative scripts
Without a consistent naming strategy, administrators spend unnecessary time searching for objects, identifying ownership, and understanding the purpose of configurations.
Good naming conventions should allow an administrator to understand an object’s purpose without opening it.
General Principles
My naming standards follow a few simple rules:
- Keep names predictable.
- Use abbreviations consistently.
- Include deployment scope when relevant.
- Avoid personal or temporary naming.
- Design for future growth.
The goal is to create names that remain understandable months or years after deployment.
Application Naming
Applications are named according to their deployment purpose.
Examples:
APP-REQ-MicrosoftVisio
APP-AVL-PowerBI
APP-UNI-AdobeReader
APP-TST-7Zip
Where:
- REQ = Required
- AVL = Available
- UNI = Uninstall
- TST = Test
This allows administrators to immediately identify deployment behavior.
Group Naming
Groups should clearly indicate both their purpose and assignment type.
Examples:
GRP-APP-REQ-MicrosoftVisio
GRP-APP-AVL-PowerBI
GRP-DEV-KioskDevices
GRP-USR-Engineering
Using prefixes such as:
- APP = Application
- DEV = Device
- USR = User
helps distinguish group functions.
Configuration Profiles
Configuration profiles should include:
- Platform
- Purpose
- Scope
Examples:
WIN-Config-BitLocker
WIN-Config-WiFi-Corporate
IOS-Config-VPN
AND-Config-KioskMode
An administrator can immediately identify what the profile manages and on which platform.
Compliance Policies
Compliance policies should remain simple and descriptive.
Examples:
WIN-Compliance-Standard
IOS-Compliance-Corporate
AND-Compliance-SharedDevices
Avoid generic names such as:
Compliance Policy
New Compliance Policy
Production Compliance
These names quickly become meaningless over time.
PowerShell Scripts
Scripts should indicate both their purpose and execution type.
Examples:
PS-Detect-LocalAdmin
PS-Remediate-TeamsCache
PS-Install-PowerToys
This makes it easier to identify remediation, detection, installation, and reporting scripts.
Benefits of Standardization
Organizations that adopt consistent naming conventions typically experience:
- Faster troubleshooting
- Easier onboarding of new administrators
- Reduced configuration mistakes
- Improved documentation quality
- Better governance and auditability
The larger the environment becomes, the more valuable naming standards become.
Conclusion
Naming conventions are not simply cosmetic. They are an operational tool that improves the manageability of Microsoft Intune environments.
Investing time in a structured naming standard early in the project helps avoid confusion, reduces administrative overhead, and creates a more scalable endpoint management platform.