SharePoint / SharePoint/sp-dev-docs
Error attempting to assign an Azure security group to a SharePoint Embedded container
@Ashlesha-MSFT is already working on this.
Since Sep 18, 2025.
- Dominant language
- PowerShell
- Stars
- 1.4k
- Forks
- 1.1k
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 12
Description
Similar to issue #9805 , I am encountering an error attempting to assign a security group permission to a SP Embedded container. I can confirm that our SP Online environment is properly configured with our Azure tenant and a Container type ID has been registered with the appropriate permissions for our App registration in Azure. We can create / manage / delete containers as well as manage the document within those containers with Application or Delegated security.
When I use Postman (Application permission, not delegated) to call the MS Graph endpoint: to create a container permission:
POST https://graph.microsoft.com/beta/storage/fileStorage/containers/{{ContainerId}}/permissions
with the following JSON body:
{
"roles": ["reader"],
"grantedToV2": {
"group": {
"id" : "e0dc3815-9c9c-4222-afd9-29921d7294ac"
}
}
}
the id is the object ID of the Security group in Azure
I receive the following error
{
"error": {
"code": "invalidRequest",
"message": "The specified user c:0o.c|federateddirectoryclaimprovider|e0dc3815-9c9c-4222-afd9-29921d7294ac could not be found.",
"innerError": {
"code": "badArgument",
"date": "2025-09-18T16:26:28",
"request-id": "efed8249-e798-4689-a02d-ea63ab7ce74c",
"client-request-id": "efed8249-e798-4689-a02d-ea63ab7ce74c"
}
}
}
I have had no issues assigning users permission to SP containers, and I also have not been able to find any documentation confirming that assigning Security Group permission SP Embedded is even possible.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.