Autopilot deployment completes without naming convention

Scenario

A device enrolls and configures, but the expected corporate hostname convention is not applied.

Recommended Resolution Path

1. Review Autopilot profile naming settings and whether the edition supports the pattern in use.
2. Check for conflicts with existing on-prem domain join or provisioning package steps.
3. Confirm whether the naming issue affects one hardware vendor or all new devices.
4. Document the post-enrollment rename workflow if the platform cannot meet the exact desired pattern.

Technician Notes

Document what changed, what confirmed the fix, and whether the issue points to a broader standards gap worth addressing for the client.