
Laim McKenzie asked a question.
Hello,
One of the guys in my team is installing a platform for a customer today, and during the Office 365 Connector setup we've found something quite interesting.
If you test the Office 365 connector with the SLM API and Office 365 Username and Password, it obviously fails due to the graph api information not being filled out. If you fill the Graph API textboxes out with any random words or characters, it returns a succesfull test connection, even though the Graph API information is incorrect.
So based on this, it looks like the Test Connection for Office 365 is only checking if those three textboxes contain data, and not if it's actually connecting to Office 365 successfully.
Has anyone else seen this? I'm going to log a ticket with Support about it as it's throwing false information, but it's interesting that no one else has picked up on this yet as far as I'm aware.
Hi
I've tested this with my config and can confirm that it doesn't pass the test if I don't have the correct details entered.... I'm running SIM v5.25 - what version are you on?
Interestingly... 5.25 as well!
@Laim McKenzie Another "nuance" is that if you do not have the 5 permission setup correctly (in the app registration) the test will succeed but then data will not flow. My work around is getting a screen shot from AAD with teh permission setup and granted ;)
Hi All,
I haven't tried in 5.25 but Snow had previously confirmed that in earlier versions the "Test connection" option definitely did not test the API connection.
This thread includes a screenshot of the required permissions.
https://community.flexera.com/s/question/0D51r00008vp8TkCAI/error-office-365-connector
Tom
We've had some interesting things happen with this today. We were trying to test the Office 365 connector and it was constantly complaining that it could not connect to the Graph API. Every time we tried to filter on domains it would fail with an error.
So we changed the log level to try to diagnose it. As soon as we changed the log level it started working perfectly. I suppose that changing the log level might have had some side effect. I thought that I'd mention it in case that helps anybody else who is testing their Office 365 connector...