Forum Discussion

Copper Contributor

May 09, 2022

Solved

Hybrid AAD Domain Join configuration profile (%SERIAL%)

Good morning, Looking to confirm my findings to solidify that this is not old information and is still accurate in 2022. The following article clearly defines in the chart that Hybrid AD Join...

Intune

mobile device management (mdm)

Mr_Helaas
May 09, 2022
Hi CrimsoWarTusk,

For hybrid devices you are very limited and you have only a prefix option, as described in the official Microsoft docs

https://docs.microsoft.com/en-us/mem/intune/configuration/domain-join-configure

For an azure joined devices autopilot profile you are able to set the %serial% or %random:xx% option.

my advice in your case is to switch to an azure joined autopilot profile because there are very limited use cases why you should create an hybrid devices.

And you can also take a look at my blog post for incrementing your autopilot naming convention

https://endpointcave.com/set-up-the-missing-naming-convention-to-increment-your-autopilot-devices/

hopefully this helps you.

kind regards,

Rene

Mr_Helaas

Iron Contributor

May 09, 2022

Hi CrimsoWarTusk,

For hybrid devices you are very limited and you have only a prefix option, as described in the official Microsoft docs

https://docs.microsoft.com/en-us/mem/intune/configuration/domain-join-configure

For an azure joined devices autopilot profile you are able to set the %serial% or %random:xx% option.

my advice in your case is to switch to an azure joined autopilot profile because there are very limited use cases why you should create an hybrid devices.

And you can also take a look at my blog post for incrementing your autopilot naming convention

https://endpointcave.com/set-up-the-missing-naming-convention-to-increment-your-autopilot-devices/

hopefully this helps you.

kind regards,

Rene

Zenithtwc

Copper Contributor

Nov 04, 2025

Thanks for the input, Rene. I appreciate the resource links.

That said, I want to clarify our position. We're a hybrid organization with significant on-prem dependencies, AD-integrated applications, GPOs, and line-of-sight requirements that make Hybrid Azure AD Join a foundational part of our identity strategy, not a "limited use case."

The current limitation in Autopilot naming for hybrid profiles, prefix-only without support for %SERIAL% is a real blocker for us. Our existing deployment workflows rely on serial-based naming for traceability and audit alignment or when a device can't be turned on and having the serial for troubleshooting vs some prefix and random number can make things easy for our techs.