About

A free tool for Microsoft Intune administrators. It builds consistent names for policies, profiles, groups and devices from a naming standard, and checks each name as you build it.

Open Build. The name is shown as segments: click one to change its value, drag it to move it, and use its × to remove it. The segments that are not in the name wait underneath, one click away. When the status says “Cleared to copy”, copy the name.

Page visits only: which page was opened, with general details such as the country and the kind of browser. Nothing about what you do in the tool is recorded. The names you build, the values you type and the segments you create are never sent anywhere; they stay in your browser.

No. NamingPilot needs no account, and everything you create is stored in your own browser.

No. Every segment can be removed, including Scope, Object, Platform, Policy type and Purpose, and the ones you keep can go in any order. The name is whatever you put in it.

Yes. In Build choose “Your own segment”, give it a name and decide whether its values come from a pick list or are typed freely. You can rename or delete your segments in Settings.

No. Lowercase, uppercase or mixed, a value goes into the name the way you typed it; only spaces and symbols are removed. If your standard wants one casing for a segment, choose it under “Casing” in Build or Settings: UPPERCASE, lowercase, or Each Word Capitalized.

Yes, in Build or in Settings. “Add value” adds a single one, “Edit values” lets you rename, remove and add values for the whole list. Both places edit the same lists, and each built-in list can be reset.

Yes, in Settings. The built-in limits are working guidelines, so set them to what the object you are naming really allows. Each limit has a button that puts the default back.

Yes. Click any shortcut in Build or Settings and press the keys you want. A few combinations belong to the browser and cannot be used.

Yes. The sun and moon button in the top bar switches between light and dark. In Settings, under Appearance, you can also choose Auto, which follows your device.

Settings can export everything to one file and import it again, on this device or another one.

Save in Build puts the name in your Library. There you can copy, star, filter and export names, or open one in Build again to change it. The export is a CSV file that opens in Excel, and Import CSV reads that same file back. You can also import a list of names you already have, for example a column copied out of Intune: NamingPilot works out the segments of each name where it can. Names saved in the previous version of NamingPilot are brought over automatically.

Naming schemas you can start from: which segments a name has, in which order, with example values. The built-in ones cover what you name in Intune day to day, such as configuration profiles, compliance policies, update rings, groups and device names. “Save as template” in Build adds your own.

Star it on the Templates page. Starred templates are listed first in Build.

It is consistent, so every name has the same shape. It is descriptive, so the name says what the item does. And it is short, while still carrying the platform, the scope and the purpose.

Only for items that change often. Versions are useful there, and clutter everywhere else.

Hyphens are the most common and the easiest to read. Underscores suit systems that handle hyphens badly. Periods can be mistaken for file extensions.