From 2f6f81acbd4fdec878479fabb8f42f0f5e771361 Mon Sep 17 00:00:00 2001 From: Jamie Klassen Date: Fri, 21 Oct 2022 16:41:15 -0400 Subject: [PATCH] mention connectivity to graph.microsoft.com Recently I was helping somebody with a Backstage installation who was hitting this error, and it turned out they needed a firewall rule to allow this connectivity. Signed-off-by: Jamie Klassen --- docs/auth/microsoft/provider.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/auth/microsoft/provider.md b/docs/auth/microsoft/provider.md index ef79127223..cbd24867b7 100644 --- a/docs/auth/microsoft/provider.md +++ b/docs/auth/microsoft/provider.md @@ -46,6 +46,12 @@ The Microsoft provider is a structure with three configuration keys: - `clientSecret`: Secret, found on App Registration > Certificates & secrets - `tenantId`: Directory (tenant) ID, found on App Registration > Overview +In order to finish signing a user in from Azure, the Backstage backend must +fetch their information from graph.microsoft.com (as seen in [this source +code](https://github.com/seanfisher/passport-microsoft/blob/0456aa9bce05579c18e77f51330176eb26373658/lib/strategy.js#L93-L95)), +so ensure that your Backstage backend has connectivity to this host. +Otherwise users may see an `Authentication failed, failed to fetch user profile` error when they attempt to log in. + ## Adding the provider to the Backstage frontend To add the provider to the frontend, add the `microsoftAuthApiRef` reference and