web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Customer experience | Sales, Customer Insights,... / FCB Microsoft Graph AP...
Customer experience | Sales, Customer Insights,...
Answered

FCB Microsoft Graph API Auth failures 400 bad request

(0) ShareShare
ReportReport
Posted on by Jerett Crumbley 188

Hey, 

Checking to see if anyone else has had this issue.  We are using D365 Online and every since the functionality that gives visibility to Teams availability has been implemented some of our users have been having issues working in the system. It appears that the system tries to do a separate authentication aside from general access to get teams availability (according to microsoft)  However some of our users get caught in a seemingly never ending auth loop.  Its hard to pin down when exactly it starts to do this. Making live troubleshooting an issue. 

There is a work around to append "&flags=FCB.MicrosoftGraphApi=false" to the end of the URL however we certainly want to fix this.  According to Microsoft, "This is by design"...    

One of the last users that did that I was able to look at the network traffic and seen a 400 bad request that triggered the auth loop.  The user has tried every browser they have and gets the same results. 

I have the same question (0)
  • nickmanny Profile Picture
    nickmanny 136 on at

    The HTTP Error 400, commonly known as "Bad Request," indicates that the server was unable to process the client's request due to malformed syntax or invalid parameters. This error occurs when the server cannot understand or interpret the request sent by the client. It may be caused by various factors, such as missing or incorrect headers, improperly formatted URLs, or invalid data in the request payload. To resolve this error, it is essential to carefully review and validate the request parameters, ensuring that they comply with the expected syntax and standards defined by the server. Additionally, verifying the compatibility of the client and server versions, encoding special characters correctly, and using appropriate HTTP methods can help prevent or rectify the occurrence of the 400 Bad Request HTTP Error.

    Expired Client Certificate

    This issue typically happens for a 2-Way TLS, when the certificate sent by the client is expired. In a 2-way TLS, both client and server exchange their public certificates to accomplish the handshake. The client validates the server certificate and the server validates the client certificate. During the TLS handshake if it is found that the client certificate is expired, then the server will send 400 - Bad request with the message “The SSL certificate error”. The solution for this problem is that procure a new certificate and upload the certificate

  • Verified answer
    Jerett Crumbley Profile Picture
    Jerett Crumbley 188 on at
    After a bunch of discussions with Microsoft on this issue. Basically what was going on is every time  your client needs to get the teams presence it forces authentication through to teams instead of caching the authentication token.  Our policy from a securance perspective is to force MFA on all this traffic which halts this process and forces a new log in and MFA.  Which is fine... if it only happens once then Dynamics should store the auth token for a set time period.  However it doesn't. Because we cannot relax those network policies we were forced to shut down this this "feature".  Hopefully Microsoft will more wisely consider how to handle this integration.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Congratulations to the February Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
ManoVerse Profile Picture

ManoVerse 180 Super User 2026 Season 1

#2
11manish Profile Picture

11manish 123

#3
CU11031447-0 Profile Picture

CU11031447-0 100

Last 30 days Overall leaderboard

Featured topics

Hide selecting Contact for potential customer when creating quote

Product updates

Dynamics 365 release plans