Forum Discussion
Error when authenticating with Default Azure Credential (CSOM)
- then you will have to wait for MS reenabling SPO accepting 'user_impersonation' scope (there is a ticket already) 🙂
any other solution involves an app registration created
Tommy-Johannessen Did you ever find a solution to this? I'm experiencing a similar issue. I'm receiving 401 Unauthorized errors while using the same way to build up a context. It's been a few months since I worked on this project, but I'm sure it worked before. Any clues?
Perneel, here is your workaround 🙂
#if DEBUG var credential = new InteractiveBrowserCredential(new InteractiveBrowserCredentialOptions() { ClientId = "the-client-id" }); #else var credential = new Azure.Identity.DefaultAzureCredential(); #endif var token = await credential.GetTokenAsync(new Azure.Core.TokenRequestContext(new[] { "https://yourtenanthere.sharepoint.com/.default" })); log.LogInformation(token.Token);The app registration the 'the-client-id' refers to looks like this
As a result, you are able to get an access token via the the Authorization Code Flow with PKCE and your browser while debugging your code locally in VS
Thank you for the reply elnurrr,
One of the issues with this approach is that we some times use our kode to setup SharePoint lists and content types on sites, where we only have access to that specific site and a user (often with MFA).
The approach we used earlier allowed us to login with the user in Visual Studio and run the code on behalf of that user. Now that is not possible, just wanted to know if it was possible to achieve the same without making a resource in Azure.
But I will keep your answer in mind as a nice workaround when possible, thanks.
- then you will have to wait for MS reenabling SPO accepting 'user_impersonation' scope (there is a ticket already) 🙂
any other solution involves an app registration created
