Creation of Node for Microsoft Entra ID (Azure AD) actions in GCC High

Questions
,
1

Hi everyone!

Our organization is currently using cloud-hosted n8n and have hit a snag when it comes to managing our Azure/Entra-related resources in Azure GCC High. The existing Microsoft Entra ID nodes only work with Azure Commercial, as Azure GCC High uses different URL endpoints (such as ending in .us insteaed of .com).

In the meantime, we’re stuck with HTTP requests straight to Microsoft Graph which works, but we would of course love to see some more ease of use. In majority of cases, especially with existing functions for the Microsoft Entra ID node, they work exactly the same with the only difference being the URL.

So, with all that said, I’m looking at resolving this and knowing that there are likely others out there with a similar issue, this could be a nice win.

What seems like the best course of action for this?

  • Submitting a feature request for the n8n team to possibly work on

  • Forking the existing node, making changes to allow for an “Environment” option and drop down. This include forking the credential: MicrosoftOAuth2Api.credentials.ts, then submitting this as a PR to merged

  • Forking the existing node, making changes to allow for an “Environment” option and drop down. This include forking the credential: MicrosoftOAuth2Api.credentials.ts, then submitting for verification as a community node.

This type of issue is something I run into with 90% of the applications we try to use, especially if they don’t have a “Government” version, so I’d love to solve this and contribute.

1 Like
2

This is a common issue with Azure GCC High environments. The most sustainable solution would be to fork the Microsoft Entra ID node and MicrosoftOAuth2Api credential, then add an “Environment” dropdown with options for Commercial and GCC High endpoints. Once implemented, submitting it as a PR to the core n8n repository would be ideal since this affects many organizations. If the core team doesn’t merge it, you could publish it as a verified community node.

3

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.