Hi, @Tanmoy Satpati
When using Azure AD in a public (commercial) cloud scenario, legacy endpoints like login.windows.net (and its more current equivalent, login.microsoftonline.com) are globally available for authenticating users. However, government clouds (such as the U.S. Government Community Cloud [GCC]) are isolated from the public cloud and have their own dedicated endpoints.
For GCC (and other sovereign or government clouds), you typically must use the service-specific endpoints. For example, for Azure Government the endpoints are in the login.microsoftonline.us domain rather than login.windows.net or login.microsoftonline.com. This separation helps ensure compliance with regional and governmental regulations.
So if you’re targeting GCC, you’ll need to update your authentication configuration to use the correct endpoint for that environment rather than relying on login.windows.net.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".