Quantcast
Channel: Azure Management Portal forum
Viewing all articles
Browse latest Browse all 4189

Hybrid joined devices marked without owner

$
0
0

Hi,

So I have an older unresolved issue that has led to this new issue:

About 1,5 years ago we decided to get further into device management in our organization.

As we had already made the switch to the E3 solution we decided to roll with Intune.

Now in order to get this to work properly we had to convert our existing on-site solution to the Azure Hybrid solution (to my understanding).

I had finally got our Windows 10 devices to be registered as Azure AD registered, and got a Bitlocker policy running, and our users could log into their myapps portal and check their bitlocker key in case something fessed up. So far so good.

But our hybrid setup simply didn't work, and the devices never registered as hybrid joined, so we were kind of stuck, and due to a ton of other projects we shelved the hybrid project for another day.

Then half a year ago in april all new devices suddenly stopped being registered in Azure AD. I couldn't fnd an explanation to this, and got no response on my support request. But while troubleshooting I found the missing pieces to get our hybrid environment up and running, and after setting up the last part of the compliance policies I've also started to see new devices both as Azure AD registered  and Hybrid joined, but the Azure registration just disappear once the hybrid join has finalized.

Now, the new issue is that the devices register without an owner, and thereby the users can't see the device from the myapps portal and access their bitlocker key.

We can, of course, provide it to them but why is this seen as a feature according to Microsoft instead of a bug??


Viewing all articles
Browse latest Browse all 4189


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>