docs: Add explicit User-Assigned Managed Identity (UAMI) example for Blob Storage binding#128222
docs: Add explicit User-Assigned Managed Identity (UAMI) example for Blob Storage binding#128222paulyuk wants to merge 1 commit intoMicrosoftDocs:mainfrom
Conversation
…orage Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
@paulyuk : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit c6dcd2f: ✅ Validation status: passed
For more details, please refer to the build report. |
PRMerger Results
|
There was a problem hiding this comment.
Pull request overview
Adds a concrete, copy/paste-friendly documentation example for configuring Azure Functions Blob Storage bindings with a User-Assigned Managed Identity (UAMI) via explicit app settings.
Changes:
- Added a new “User-assigned managed identity” subsection to the Blob Storage connection docs
- Included a properties table and a full JSON app settings example
- Added guidance on when UAMI is recommended
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| | Property | Environment variable template | Description | Example value | | ||
| |---------------------------|-----------------------------------------------------|--------------------------------------------|---------| | ||
| | Blob Service URI | `<CONNECTION_NAME_PREFIX>__blobServiceUri` | The data plane URI of the blob service. | `https://mystorageaccount.blob.core.windows.net` | | ||
| | Queue Service URI | `<CONNECTION_NAME_PREFIX>__queueServiceUri` | The data plane URI of the queue service (required for blob triggers). | `https://mystorageaccount.queue.core.windows.net` | | ||
| | Credential | `<CONNECTION_NAME_PREFIX>__credential` | Must be set to `managedidentity`. | `managedidentity` | | ||
| | Client ID | `<CONNECTION_NAME_PREFIX>__clientId` | The client ID of the user-assigned managed identity. | `00000000-0000-0000-0000-000000000000` | |
There was a problem hiding this comment.
The table rows/header are prefixed with double pipes (||), which will render an extra empty column and often breaks Markdown table formatting. Use a single leading pipe (|) for the header, separator, and each row so the table renders correctly.
|
|
||
| #### User-assigned managed identity | ||
|
|
||
| To use a user-assigned managed identity, add the `credential` and `clientId` properties in addition to the service URI: |
There was a problem hiding this comment.
This sentence refers to a single 'service URI', but the section/table introduces two URIs (blobServiceUri and queueServiceUri). Consider rewording to 'service URIs' (or explicitly call out blob vs queue URIs) to avoid confusion.
| To use a user-assigned managed identity, add the `credential` and `clientId` properties in addition to the service URI: | |
| To use a user-assigned managed identity, add the `credential` and `clientId` properties in addition to the blob and queue service URIs: |
|
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
bot
added
the
aq-pr-triaged
3 participants
Summary
This PR adds a clearer example showing how to configure Blob Storage connections using a User-Assigned Managed Identity (UAMI) with explicit app settings.
Problem
The existing documentation mentions
credentialandclientIdproperties for user-assigned managed identities but lacks a concrete JSON example.Solution
Added a new "User-assigned managed identity" subsection with:
Changes
includes/functions-storage-blob-connections.md: Added UAMI configuration exampleRelated