06/30/2023
03:07 AM
- last edited on
06/30/2023
07:11 AM
by
Dave
Do you have a backport fix that will remove the requirement to use the Azure AD Graph Api from your connector code in version 5.5 SP3.10
Solved! Go to Solution.
07/02/2023 10:12 PM - edited 07/02/2023 10:13 PM
I believe this change was backported to 5.5SP3.10 as well.
You should be able to see the below connection params if the fix is available-
AUTHENTICATION_ENDPOINT, MICROSOFT_GRAPH_ENDPOINT, AZURE_MANAGEMENT_ENDPOINT
Populate these connection params with the below values-
AUTHENTICATION_ENDPOINT- https://login.microsoftonline.com/
MICROSOFT_GRAPH_ENDPOINT- https://graph.microsoft.com/
AZURE_MANAGEMENT_ENDPOINT- https://management.azure.com/
Add the Microsoft Graph API permissions to the Application instead of the AAD Graph APIs as mentioned in the doc- https://docs.saviyntcloud.com/bundle/AzureConf-v2022x/page/Content/Registering-an-Application-in-Azu...
The connection should be successful.
Please let me know if there is any query.
07/25/2023 05:14 AM
Hi,
We have tried populating the connection params with the above-mentioned values and added the Microsoft Graph API permissions instead of AAD Graph APIs but still the connection is going into the failed state.
07/27/2023 03:38 AM
@saidnya_naik Please try removing the forward-slash (/) at the end of the above URLs.
AUTHENTICATION_ENDPOINT- https://login.microsoftonline.com
MICROSOFT_GRAPH_ENDPOINT- https://graph.microsoft.com
AZURE_MANAGEMENT_ENDPOINT- https://management.azure.com
07/31/2023 05:23 AM
Hi,
As suggested, tried removing the forward slash (/) from the end of the URLs but the connection is still failing.
08/02/2023 01:40 AM
@saidnya_naik Please open an FD ticket with the details and logs so that the Engg team can look into it.