I spent about 8 hours pulling my hair out trying to configure everything, and was finally able to succeed after disregarding this piece of advice:
On your token request, set the scope to "https://sts.//.default", where is replaced with the Account Domain for your Azure Spatial Anchors account.
My spatial anchor account domain is clearly listed as 'southcentralus.mixedreality.azure.com', but was only able to obtain the correct configuration by setting the scope to "https://sts.mixedreality.azure.com//.default" (without southcentralus)
(using msal node libarary)
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
ID: 7d43bc57-798b-d3a4-5f31-a22f9ef99b2d
Version Independent ID: dff6c910-70a8-6441-c67a-c66ec5e01cbb
I spent about 8 hours pulling my hair out trying to configure everything, and was finally able to succeed after disregarding this piece of advice:
On your token request, set the scope to "https://sts.//.default", where is replaced with the Account Domain for your Azure Spatial Anchors account.
My spatial anchor account domain is clearly listed as 'southcentralus.mixedreality.azure.com', but was only able to obtain the correct configuration by setting the scope to "https://sts.mixedreality.azure.com//.default" (without southcentralus)
(using msal node libarary)
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.