Allow Use of Microsoft Authenticator OTP in Azure AD
Hi All, We wanted to enabled number matching and Passwordless with Microsoft Authenticator app and when I go to there I could see the below setting under configurations. But I wanted to make sure what that setting is and what it the recommended configurations for this "Allow Use of Microsoft Authenticator OTP" before configure in production environment. appreciate if anyone could help me on this. Thanks, DilanHybrid Azure AD join devices MDM set to "none"?
Good afternoon, We have recently upgraded all of our servers and as part of that I'm re-configuring Azure AD Connect for the hybrid environment. Users are syncing properly. Devices, however, seem to fail to be picked up by Intune and thus, MDM. IT is set to "none" and on top of that is not replacing the existing record for the device, so currently there's a Hybrid Azure AD join device and a Azure AD registered record assigned to the user that uses it (myself). I'm trying to use auto-enrollment via GPO, the specific GPO is "Enable Automatic MDM enrollment using default Azure AD credentials". Something I've noticed (and if memory servers me well), is the fact that the generated task in task scheduler is named differently. If I remember correct, the name should match or be similar to that of the GPO, it is now called "Schedule created by enrollment client for automatically enrolling in MDM from AAD". So I'm not too sure if the policy is, for whatever reason, generating the wrong task? At any rate, below is the information of one of the devices: | Device State | +----------------------------------------------------------------------+ AzureAdJoined : YES EnterpriseJoined : NO DomainJoined : YES DomainName : DOMAIN SSO State | +----------------------------------------------------------------------+ AzureAdPrt : NO AzureAdPrtAuthority : EnterprisePrt : NO EnterprisePrtAuthority : I'm aware that AzureAdPrt is set to NO, but I understand that isn't an issue if you are trying to enroll via default user credentials? (Correct me if I'm wrong). As for Intune, auto-enrollment is activated for everyone and anyone with the correct license. It has been a while since I last worked with this and perhaps I'm missing something obvious, but having look at Microsoft's docs and following some of the trouble shooting advice, I cannot see anything wrong with my setup. Please, if you need any more information do let me know. Thank you
Microsoft Edge on iOS and Android now supports conditional access and single sign-on
Microsoft Enterprise Mobility + Security (EMS) is excited to deliver Azure Active Directory conditional access protection for Microsoft Edge on iOS and Android. This integration expands the Microsoft Intune management capabilities as you deploy Microsoft Edge for the best browsing experience across all endpoints in the enterprise. Users get easy, secure access to Office 365 and all your web apps that use Azure Active Directory, with the same application management and security capabilities that previously required Intune Managed Browser.
Company portal failing to install error 0x87D1041C
Hello Everyone, I have added company portal (offline version) from Microsoft store for Business and deployed it to 6 autopilot enrolled windows 10 laptops. All laptops are with same hardware & configurations. Out of all laptop, company portal application is getting failed in one windows 10 laptop. I have tried to uninstall and re-install it but it's showing same error every time in that particular laptop. However apps are getting published in company portal in that laptop. then why in Endpoint manager it's showing failed to install with error code 0x87D1041C.-2016281111 error Intune windows 10 update rings Using deadline settings
[Edited] Hello everyone, hoping you all are having a good day. I need some inputs on my current Windows 10 update rings policy. I set the deadline settings as shown below to multiple pilot devices. These devices are identical in all hardware but has different windows 10 builds (1909, 1709, 1903, 20H1, 21H2). Devices with Windows 10 1709 builds has been successful but I got this error "-2016281111 (Not applicable for this device)" on other versions. Policy Applied : User group User License : M365 Business premium and Windows 10 Enterprise E3
