An Azure event routing service designed for high availability, consistent performance, and dynamic scale.
Hi @Ade Jabar - welcome to the Microsoft Azure QnA.
Why does destination validation report the account missing when both account and queue resolve successfully through ARM?
Look at which resource the error names. It reports resourceId: <storage-account-resource-id>, the storage account, not the queue. That is the same scope the documentation requires for the role assignment, which is covered below.
Is queue-scoped Storage Queue Data Message Sender sufficient for managed-identity destination validation, or is another narrowly scoped permission required?
The documented requirement is the storage account, not the queue. From Event Grid managed identity delivery:
“The identity must be a member of the Storage Queue Data Message Sender role on the storage account. It must also be a member of the Storage Blob Data Contributor role on the storage account that you use for dead-lettering.”
You have it assigned at the exact queue scope. Azure RBAC does not inherit upward, so an assignment at the queue does not grant anything at the account. I would correct that and retest before anything else, since it is the only documented difference between your configuration and Microsoft’s example.
I could not establish your remaining two questions from the documentation, on retrieving the async operation’s final status and on whether the configuration is supported with shared-key access disabled.
One separate thing worth a test. The CLI example builds the endpoint as the full queue resource path:
queueid="$storageid/queueservices/default/queues/<QUEUE NAME>"
and passes it to --delivery-identity-endpoint. Your ARM PUT used resourceId plus queueName, which matches the REST schema and is not wrong, but if you retry through the CLI that is the documented form.
Help make this community better for everyone: if this answer resolved your issue, please accept it or leave an upvote. If not, share more details in a comment so we can continue the discussion and find the right solution.