Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • And not coupled to either Azure nor Keycloak Commented Mar 16, 2023 at 7:53
  • I may not fully understand your comment, it seems to make some assumptions. Do you mean by using an external service you get some de-coupling? Commented Mar 16, 2023 at 10:41
  • 1
    @linus, what Laiv meant by introducing your own identity service (acting as a proxy to AzureAD in your case), you abstract the Azure dependency behind your own proxy over which you have full control, pretty much introducing an anti-corruption layer. This is usually to your benefit, as potential change impacts due to changes in AzureAD are isolated to a single place in your ecosystem - the identity service. Commented Mar 16, 2023 at 19:00