Personalized Community is here!
Quickly customize your community to find the content you seek.
Now Available in Community - New TechTalk Videos for 2020
Read More about New TechTalks for 2020
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
I have a newly set up demo environment and I am trying to import users from our Azure Active Directory. When doing this I get the error:The service you are trying to reach is currently unavailable. Please contact your System Administrator for further assistance.
Seems I have the same issue on all our environments.
Is this an error in Azure? Anyone else got the same error?
You get this error when you are using the downloaded VM. I do have the same issue in a local box. As workaround you can setup the users without using the wizard.
The feature is working on Dynamics 365 deployed on Azure.
Thanks... unfortunately this is not a downloaded VM... this is deployed from LCS to Azure :-)
I will add the manually for now but I would be interested in knowing if anyone else has this issue right now
So my assumption was incorrect. I have not seen this problem before on Azure deployments. can you confirm you have administrator rights in Dynamics 365 and possibly also on AAD?
I am administrator in Dynamics 365. I do not have admin rights in Azure AD but that have not been an issue before
No one that can test this on their own environment to see if you have the same issue... Since it affect all of our environments I think it is an issue in Azure.
If its a Azure AD issue, contact Microsoft support.
-Ravi Theja Madisetty
I had a check today at a customer. It's working correctly on their environment. This is the fall release.
What exact topology are you using and do you still have the same issue? Probably you can use e.g. Fiddler to monitor network traffic.
Is your demo environment under the same Azure subscription meaning the same tenant ??
Yes... the environment is in the same tenant...
The issue has been resolved now by it self... seemed it was an Azure issue after all
It is working now... think it was a temporary Azure AD issue
Hello, Do you know the cause of this issue? I am seeing the same issue occurring in our environments.
Can you please attach error screen, if possible ?
Ravi Theja Madisetty
I am facing similar issue.
error while importing user,
The service you are trying to reach is currently unavailable. Please contact your System Administrator for further assistance.
Please suggest me solutions if you have any.
thanks in advance.
Please also tell me what exact configuration you have done in Azure AD as well as in D365 account.
I had faced same issue couple of days back, it got resolved after server restart.
One of my colleagues had faced the similar issue they had resolved with help of Microsoft support. This is a timeout issue, increasing WaitTime in the web config file will resolve the subjected issue--------------------------------------------------------------------------Change the MaxListTaskWaitTime and MaxTaskWaitTime in web.config to: <add key="GraphApi.MaxListTaskWaitTime" value="100000" /> <add key="GraphApi.MaxTaskWaitTime" value="60000" />
webconfig file path: %ServiceDrive%\AosService\WebRoot\ find "web.config file "
This issue explained in this KB article, please check the details in LCS:
KB 4338123User login and session creation can fail.
I am unable to locate the KB, did a server restart resolve the problem or the above,, please confirm KB details
Once this kind of issue resolved after server restart.
Another time, modifying webconfig file solved subjected issue.
Change the MaxListTaskWaitTime and MaxTaskWaitTime in web.config to:
<add key="GraphApi.MaxListTaskWaitTime" value="100000" />
<add key="GraphApi.MaxTaskWaitTime" value="60000" />
Business Applications communities