---
title: "Comment by Ryan Pertusio on \"Fix for incorrectly named devices enrolled using Autopilot through Azure Automation\" | Hashnode"
description: "Thanks for this! You'll actually notice that the correct profile does make it to the device. I put in a ticket. Microsoft Support says there's a 3 minut"
url: "https://hashnode.com/posts/fix-for-incorrectly-named-devices-enrolled-using-autopilot-through-azure-automation/6377cf4fface77f5a7bc0709/comment/6378342a1c7f8b86d18f6d59"
---

[Discussion](https://hashnode.com/posts/fix-for-incorrectly-named-devices-enrolled-using-autopilot-through-azure-automation/6377cf4fface77f5a7bc0709)

Comment [Fix for incorrectly named devices enrolled using Autopilot through Azure Automation](https://hashnode.com/posts/fix-for-incorrectly-named-devices-enrolled-using-autopilot-through-azure-automation/6377cf4fface77f5a7bc0709)

[Ryan Pertusio](https://hashnode.com/@rpertusio)

[Nov 19, 2022](https://hashnode.com/posts/fix-for-incorrectly-named-devices-enrolled-using-autopilot-through-azure-automation/6377cf4fface77f5a7bc0709/comment/6378342a1c7f8b86d18f6d59)

Thanks for this!

You'll actually notice that the correct profile _does_ make it to the device. I put in a ticket. Microsoft Support says there's a 3 minute hard-coded timeout. If the work (in that 3 minutes, including PC rename) isn't completed in time, it moves on, leaving a generic name. It's apparently not going to be an easy one to fix on MS side.