Harken, good fellow, and lend thine ear, for I shall weave a tale of Microsoft PowerShell in the noble tongue of yore.

In the kingdom of Microsoft, there existed a potent sorcery known as PowerShell, a wondrous command-line shell and scripting language. Like a skilled enchanter, PowerShell bestowed upon its users the power to command the arcane forces dwelling within their devices, be they castles of computing or humble machines.

Verily, PowerShell was akin to a knight's trusty squire, aiding them in their noble quest for mastery over the realm of digital dominion. With a mere flick of the wrist and the utterance of its commandments, PowerShell could summon the spirits of automation, bestow the gift of scripting, and wield the might of administrative control.

Much like the scribe who transcribes the words of the learned, PowerShell could manipulate vast swaths of text, both reading and writing, with the grace of a quill upon parchment. It possessed the knowledge to traverse the hidden depths of files and directories, seeking out secrets and illuminating the mysteries that lay therein.

But PowerShell's true strength lay in its ability to commune with the spirits of software and systems. It conversed fluently with the applications and services that dwelled within the digital realm, issuing commands and receiving answers in the language of the machines. From configuring networks to managing databases, PowerShell was a trusted ally, loyal to those who sought to tame the chaos of the digital world.

With PowerShell, a humble user could write incantations, known as scripts, to automate repetitive tasks, granting them respite from the burdensome toil of manual labor. These scripts were like enchanted scrolls, brimming with wisdom and instruction, allowing the wielder to perform feats that would otherwise require great effort and time.

In truth, PowerShell was a tool of great versatility, able to bend to the will of its user, whether they be a simple scribe or a learned wizard. It was a bridge between the mortal realm and the ethereal realm of machines, granting access to powers that would have seemed unimaginable in times of yore.

Thus, the tale of Microsoft PowerShell, the mystical command-line shell and scripting language, unfolds. May it inspire thee, dear reader, to embark upon thy own quest for mastery over the digital realm, armed with the knowledge and power bestowed by this ancient sorcery.

So I've got a weird situation. We have one iOS (iphone 13 with 16.5) device only that is having issues completing the enrollment process.

download and sign into company portal

sign into the company portal

installed the management profile (confirmed)

device reports as not registered by company portal

the device not being registered is causing CA policies to fail for the device so the user can't setup their apps like outlook or teams.

I've also confirmed there isn't another management profile installed for another mdm.

I've walked the user through the enrollment process a few times, with and without the authenticator app installed and setup. the device doesn't show as registered in the authenticator app either. trying to register the device in authenticator just gives an generic error saying something went wrong.

I did come across something online about supervised devices in this state when the device id in azure ad is all zeros (https://learn.microsoft.com/en-us/mem/intune/apps/app-configuration-policies-use-ios#configure-the-company-portal-app-to-support-ios-and-ipados-devices-enrolled-with-automated-device-enrollment) however in this case the device id is populated.

I've re-enrolled one of my devices to walk through the setup process to make sure it's not something with the CA policies or something else. as far as I can tell this person is setup just like everyone else that is using mdm.

Hopefully someone has an idea, because i'm out of ideas on this.