[BUG]: team-sync/group-mappings not working in EMU Data Residency Enterprise

[tvriesde]

What happened?

Goal: Create team and connect to idp group for team sync.

The following code works correctly in a GitHub personal users Enterprise Organization.

But fails when running in an GitHub Enterprise EMU, European Data Residency (ghe.com) environment.

Error given by the GH API:
This team is not externally managed. Learn more at https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github - https://docs.github.com/rest/teams/team-sync#create-or-update-idp-group-connections

Team sync has been enabled for both enterprises. And works when configuring manually using the GH web portal.

Versions

"@octokit/rest": "^21.1.1",

Relevant log output

This team is not externally managed. Learn more at https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github - https://docs.github.com/rest/teams/team-sync#create-or-update-idp-group-connections

Code of Conduct

• I agree to follow this project's Code of Conduct

[github-actions]

👋 Hi! Thank you for this contribution! Just to let you know, our GitHub SDK team does a round of issue and PR reviews twice a week, every Monday and Friday! We have a process in place for prioritizing and responding to your input. Because you are a part of this community please feel free to comment, add to, or pick up any issues/PRs that are labeled with Status: Up for grabs. You & others like you are the reason all of this works! So thank you & happy coding! 🚀

[wolfy1339]

This isn't an Octokit bug. I can't help you there as i have no experience with GHES.

[tvriesde]

This is not GHES, its GHEC Enterprise Managed Users with Data Residency enabled. Its an option you can order with GH in Europe.

https://docs.github.com/en/enterprise-cloud@latest/admin/data-residency/about-github-enterprise-cloud-with-data-residency

[wolfy1339]

GHES/GHEC, doesn't matter, I have no experience with either, and cannot help you here. The call seems fine to me

You'll probably need to reach out to GitHub support, this isn't an Octokit bug.