This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(25.6, 80%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKK%3C/text%3E%3C/svg%3E)
I would like to get the support for the below issues which I am facing in my infra
We have enabled intune infra for AutoPilot.
Machines were successfully enroled with Auto Pilot process.
My machine is enrolled and I am successfully logged into the device. But I am trying to check with multiple accounts to login to the same device, but unfortunately I couldn't login with other accounts and receiving the error as
"we are unable to connect you right now. check your network connection or try again later"
Trying with 3 type of accounts
There is no luck and cant login to the device. is there any restrictions or any configurations required to have the account to login to Azure Joined device?
On Prem & Azure sync account, I can login to the onprem servers and desktops without any issue, its impacting only Azure joined device. What will be the issue? Any pointers will be appreciated to fix this issue
Thanks in advance
Karthick
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(89.60000000000001, 81%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERA%3C/text%3E%3C/svg%3E)
Are they using any VPN?
Check the event viewer and log files and see if there is any error there?
Are you able to ping the Azure from those devices?
Hi Reza, thanks for the reply.
Machine is connected through LAN & also tried through WAN. Its corporate network and not VPN.
Issue is, unable to login to the device on first login. Its throws the error that "we are unable to connect you right now. check your network connection or try again later"
But the same account is working fine to login to the onprem device and VDI
So checking event log or ping will be done post the login.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(163.2, 33%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECW%3C/text%3E%3C/svg%3E)
Can I know have you configured limiting users who can join their devices to AzureAD: Go to Azure Portal > Azure Acitve Directory > Devices > Add memebers who can join devices to Azure AD.
We are at pilot, only users part of Azure AD group can join machines under Azure and the accounts which I am trying is part of the group.
Here the situation is not for registering the device but login. Machine is already enrolled into intune with other credentials. For testing purpose, we tried to login to the same machine with another user credentials which is already added into Azure group. But we cant login with the said error of unable to connect you now, try again later.
I have done a lot of research and consult Azure AD support engineer these days. As there is part of Azure AD group has occurred this issue, we may need to collect logs and troubleshoot at the backend. It is highly suggested to create an online support case for Azure AD to resolve this issue more effectively. Here is the link: Find help and open a support ticket for Azure Active Directory
Just making sure, but are you using the complete fqdn to login? Have you tried using @onmicrosoft.com domain instead? Also, maybe explore the idea of using shared multi user device settings profile?
Thanks Rahul for your reply. Yes currently we are using the FQDN login to the devices and same tried for this testing as well.
Regarding the second part, is this settings in Intune or somewhere?
Yes, it is one of the device configuration profile policy in Intune. You can find the details in the official link below.