Added Documentation Page for Bulk Container Permission Creation via D…

[RushwantKoppolu]

…elta Patch

Important

Required for API changes:

• [] Link to API.md file: N/A (no new API introduced; documentation for existing Delta
• [] Link to PR for public-facing schema changes (schema-Prod-beta/v1.0.csdl): N/A (no schema changes)
• [] Attach the documentation plan generated for AI-assisted docs authoring and validation to help speed up content review.

---

Add other supporting information, such as a description of the PR changes:

This PR introduces a new API documentation page for bulk permission creation using Delta Patch on fileStorageContainer resources in Microsoft Graph.

It documents:
Adding up to 10 permissions in a single request
Delta Patch request structure (PATCH + value[])
Partial success behavior for batch operations

This PR does not modify existing Create (POST) or Update (PATCH) permission documentation.

---

Important

The following guidance is for Microsoft employees only. Community contributors can ignore this message; our content team will manage the status.

After you've created your PR, expand this section for tips and additional instructions.

• do not merge is the default PR status and is automatically added to all open PRs that don't have the ready to merge label.
• Add the ready for content review label to start a review. Only PRs that have met the minimum requirements for content review and have this label are reviewed.
• If your content reviewer requests changes, review the feedback and address accordingly as soon as possible to keep your pull request moving forward. After you address the feedback, remove the changes requested label, add the review feedback addressed label, and select the Re-request review icon next to the content reviewer's alias. If you can't add labels, add a comment with #feedback-addressed to the pull request.
• After the content review is complete, your reviewer will add the content review complete label. When the updates in this PR are ready for external customers to use, replace the do not merge label with ready to merge and the PR will be merged within 24 working hours.
• Pull requests that are inactive for more than 6 weeks will be automatically closed. Before that, you receive reminders at 2 weeks, 4 weeks, and 6 weeks. If you still need the PR, you can reopen or recreate the request.

For more information, see the Content review process summary.

[learn-build-service-prod]

Learn Build status updates of commit 074a7d0:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
api-reference/beta/api/filestoragecontainer-deltapatch-permissions.md	⚠️Warning		Details
api-reference/beta/includes/permissions/filestoragecontainer-deltapatch-permissions-permissions.md	✅Succeeded
api-reference/beta/resources/filestoragecontainer.md	✅Succeeded

api-reference/beta/api/filestoragecontainer-deltapatch-permissions.md

• Line 4, Column 9: [Warning: author-not-found - See documentation] Invalid value for author: 'rkoppolu' is not a valid GitHub ID.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

[lilealdai]

Isn't this supposed to be auto-generated?

[lilealdai]

Delta patch permissions

[lilealdai]

We will review beta first, after that, we can add the v1.0 doc in this same PR.

[RushwantKoppolu]

@RushwantKoppolu please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

• (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

• (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

@microsoft-github-policy-service agree company="Microsoft"

[learn-build-service-prod]

Learn Build status updates of commit fbc2164:

✅ Validation status: passed

File	Status	Preview URL	Details
api-reference/beta/api/filestoragecontainer-deltapatch-permissions.md	✅Succeeded
api-reference/beta/includes/permissions/filestoragecontainer-deltapatch-permissions-permissions.md	✅Succeeded
api-reference/beta/resources/filestoragecontainer.md	✅Succeeded

For more details, please refer to the build report.

[lilealdai]

Important is not showing correctly

[lilealdai]

Collection(permission) like the roles?

[FaithOmbongi]

@RushwantKoppolu - We don't accept contributions for schema-related changes through the public repo. Please move these changes to the private repo instead. See https://aka.ms/msgraphcdk for more info.