There are still a few portions of the Hybrid configuration that require using the web portal. Can you migrate existing hybrid tenants to the Azure portal so we can perform these actions without requiring Silverlight?6 votes
Not sure how to mark this one. At this point it’s not really a question of migrating hybrid tenants to Azure, since we announced deprecation of hybrid configurations. But we did move all MDM functionality from Silverlight to Azure in preparation for removing MDM from the Silverlight console, so it’s sort of complete. I’m just going to call it declined, but either way there are solutions now, and you get your votes back.
We support co-management, which enables you to concurrently manage Windows 10 devices by using both ConfigMgr and Intune.
We encourage you to start planning your migration for MDM from the ConfigMgr console to Azure and to shift your UserVoice votes to MDM features for Intune. For more information, see https://aka.ms/hybrid_notification
Thank you for your feedback, and thank you for using Intune and Configuration Manager!
Could you improve the Intune portal to display an appropriate warning message if the MDM authority is set to something other than Intune?
Currently if the MDM authority is set to SCCM the portal just fails with inexplicable errors like this:
> An error occurred whilst fetching MDM Authority
It would also be helpful to expose the current MDM Authority in the tenant settings somewhere.
OK, thanks, but in that case I’m going to say this is declined, given that MDM authority is going to become less of a barrier now that we will support “mixed” authority with Configuration Manager and Intune.
Add a portal view that shows Policy Conflicts - specifically, Compliance Policy conflicts - and the source of the policy - On-premises AD, Exchange ActiveSync, Exchange Online, SCCM, Azure AD to name a few.
This 'Policy Conflicts' portal view was available in the Intune Classic Portal, but appears to have been removed from the Azure Intune Blade (for reasons unknown).1 vote
I checked on this and the reason we don’t have a “policy conflict” view in the Azure portal is that policy conflicts went away – the most stringent always wins. That’s why we didn’t create that view as we started moving things over.
You can see more information in the FAQ here
Also, one of our MVPs wrote an article about how to see what policies are applied.
I hope this helps! I’m going to mark this request declined, since it is “moot” at this point. But if you see other aspects of troubleshooting policy that we haven’t addressed yet, please file them. :-)
- Don't see your idea?