User Profile
Merlin
Copper Contributor
Joined 4 years ago
User Widgets
Recent Discussions
Edge iOS authentication loop on Intune-managed device with Microsoft Enterprise SSO plug-in enabled
Hello Team, I'm experiencing a pretty weird issue with Edge on an iPhone 12 (16.5) enrolled in Intune with user affinity. I have an Azure AD user logged into the browser with sync enabled. The user is logged in to all Microsoft apps using the Microsoft Enterprise SSO plug-in for Apple devices.. Here's a .gif of the issue: Whenever I attempt to login to any website that uses Azure AD as its idP, the browser gets stuck at the login.microsoftonline.com endpoint and eventually enters what appears to be a loop with the Microsoft Authenticator app. This behavior is exclusive to Edge. All other Microsoft apps authenticate the user successfully using the SSO plug-in. Here are the Intune management settings enabled on the device: Device configuration policy settings Single sign-on app extension is enabled SSO app extension type: Azure AD Additional configuration for single sign-on app extension App configuration policy settings for Edge App protection policy for all Microsoft apps In addition to those settings, I do also have Safari hidden via a device restrictions policy. The goal is for all users to use Edge only. Any idea what might be driving this issue?5.4KViews0likes9CommentsCompany Portal freezing iPhone after setup assistant is complete
Hello Team, I am brand new to Intune and have a bit of a tight deadline to establish a baseline configuration for our mobile devices (iOS/iPadOS only). I'm seeking some clarification on the expected OOBE behavior for the Intune Company Portal app. Per Microsoft's recommendation, I am deploying the Company Portal app via VPP. In the default ADE enrollment profile, I have the following settings: User affinity: Enroll with User Affinity Select where users must authenticate: Company Portal Install Company Portal with VPP: Use token (specified user) Run Company Portal In Single App Mode until authentication: Yes In app assignments, I have the following: Intune Company Portal (VPP): Required for All devices as an application that can't be removed. Microsoft Intune Company Portal: Unassigned So, my expectation under this configuration is that the company portal application would automatically install and open in single-app mode shortly after users setup assistant is complete. However, what's happening is that the Company Portal app installs silently and does not open. It appears on the Home screen after setup assistant closes. When I open the Company Portal app, the entire iPhone is frozen and must be force-started. After the force restart, the Company Portal application opens in single-app mode and requires authentication as I would expect. But the desired behavior is for this to happen after setup assistant is complete without freezing or having to restart the device. This behavior is consistent across multiple devices. Is there anything in my configuration that is causing this behavior?3.3KViews0likes1CommentEnabled Services on Microsoft 365 commercial licenses in AAD
To preface this, the controls I'm referring to can be found using this path: Azure Portal > Azure Active Directory > Users > (select user record) > Licenses > (select Microsoft 365 commercial license) We had an issue wherein SMTP authentication from our MFPs was failing. While investigating, we discovered that the Exchange Online (Plan 1) service that's packaged with the Microsoft 365 Business Standard license was turned off on the user that we use for this implementation. Because of that, the user's mailbox disappeared from exchange. After enabling Exchange Online (Plan 1) in the AAD admin center, everything started working again. While it's troubling that this service was seemingly turned off without our intervention, what's more troubling is that I became curious and started checking other user records--including my own. I found that the Exchange Online (Plan 1) service was turned off--yet my mailbox was working just fine. I found other users with the same anomaly. Does anyone have any insight on how or why this would happen? For additional background, we transitioned from Exchange 2013 on-prem to Exchange Online back in 10/2020. We're not operating on hybrid exchange. It's fully online.Solved2.9KViews0likes2Comments