[BUG] GCC: Unable to create a viable connection

[mlanza]

Describe the bug
Our team is unable to use the tool to connect to any of our endpoints. We are in the GCC, which is why I think this issue may not have been more widely reported. I am guessing here, but I wonder if some lack of parity in the environments has your hardcoded endpoints working for most users, but not GCC users.

System.Exception: Failure Response for request to WebAPI //api/discovery/v2.0/Instances : StatusCode=NotFound :
RequestID=55e279ef-7c63-449f-b6ea-3ea952bacf98 :
Failure Response for request to WebAPI //api/discovery/v2.0/Instances : StatusCode=NotFound :
RequestID=55e279ef-7c63-449f-b6ea-3ea952bacf98 : ERROR REQUESTING ORGS FROM THE DISCOVERY SERVER
SERVEROperation returned an invalid status code
‘NotFound’ Exception while trying to connect Discovery Server, (Global Discovery) URI is =
https://globaldisco.crm9.dynamics.com//api/discovery/v2.0/Instances
One or more errors occurred. => Operation returned an invalid status code ‘NotFound’ No Organizations Found,
Searched online. Region Setting = NorthAmerica2
No Organizations Found,

To Reproduce
Try to create a connection the usual way and enter credentials. It fails to establish a connection.

Expected behavior
I would expect the wizard to result in a viable connection.

Additional context
We recently updated the tool. It has you do that. To rule out a bad cache, I uninstalled the existing copy, deleted the cache on my box, and reinstalled. No help.

[mlanza]

Fortunately, I was able to define a connection string another way and get in. So the issue is with the Wizard itself. It walks you through setting up the connection string, the way we've always done it. That way is broken.

[MscrmTools]

Can you precise what connection type you tried to create?

[mlanza]

I used the Connection Wizard. It starts by asking for Environment url. On the next screen, Domain, Username, and Password. Domain is locked and can't be entered. It's not like I have any control over the path. It's a wizard. It walks me along its default path.

I got around it by working with ChatGPT to invent a good connection string. After some iteration I got it working, so this is low priority now. It's just that the default path (what the whole team, a couple non-devs and I, have come to rely on) no longer works.

[frick-brian]

This same thing is happening to us with new connections pointing toward GCC / crm9 subdomain.

My old build of XRMTB (24.9.69) has no problems with EXISTING connections, but new conns to GCC are resulting in same error as OP posted in the bug.

My colleague was having issues specifically with SQL4CDS, so he upgraded to latest XRMTB, and he cannot use user/pass authentication at all, same error.

ClientID/ClientSecret works for login, but that isn't how we typically run XRMTB and removes some of the auditabilty we enjoy with named accounts using XRMTB for system changes.

[rlmeans]

We are experiencing the same issue for existing and new connections to GCC endpoints. We are unable to use the interactive authentication flow and get the same error seen above. Seems like MS may have changed some discovery endpoints? Shouldn't region setting be GCC not NorthAmerica2?

Thanks for any help with this. We also do not want to use client ID / secret for auditability reasons.