I’m currently engaged in a project that involves deploying an Angular frontend and five .NET 8 microservices, each backed by Azure SQL (PaaS). These components are secured through Azure AD, with bearer tokens facilitating secure communications. Our deployment strategy requires the microservices to be hosted across three geographic regions (AMERICAS, EUROPE, and ASIAPACIFIC), while the frontend will only be deployed in EUROPE.
To manage authentication across these distributed components, we plan to use Microsoft EntraID with separate registrations for the APIs in each region, and one for the frontend. We are considering the implementation of MSAL v3 to handle the authentication flows.
I am looking for insights on the best architectural practices to implement this setup effectively.
Specifically, I am interested in:
- Strategies for configuring MSAL v3 to manage authentication efficiently across multiple regions.
- Considerations for maintaining high performance and reliability in such a distributed environment.
- Any potential pitfalls or challenges that might arise with this type of deployment.
If anyone has experience or advice on setting up a similar architecture, or can share best practices for using MSAL v3 in a multi-regional scenario, your input would be invaluable.
Can anyone please help me here by providing their guidance? Any help would be greatly appreciated.