Add resource group creation step for Event Grid
Added instructions for creating a resource group before creating an Event Grid namespace.
I ran into two errors when trying out this sample article.
- First, I got an error that the location parameter needs to be specified.
- Then, after I supplied the location parameter, it kept telling me that the resource group is not found.
So, it looks like, the resource group needs be created prior to creating the namespace.
Second, it looks like the location parameter is needed to make this command work.
Here are the errors I ran into.
InvalidArgumentValue: Missing required field: --location
(ResourceGroupNotFound) Resource group 'rg1142' could not be found.
Code: ResourceGroupNotFound
Message: Resource group 'rg1142' could not be found.
@Jay-study-nildana : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.
Learn Build status updates of commit db3bfb7:
:white_check_mark: Validation status: passed
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/event-grid/mqtt-publish-and-subscribe-cli.md | :white_check_mark:Succeeded |
For more details, please refer to the build report.
@george-guirguis
Can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged" @MicrosoftDocs/public-repo-pr-review-team
@.@.>, please review and approve this contribution to the doc.
Thanks, George
From: Tracey Torble @.> Sent: Monday, December 15, 2025 8:06 AM To: MicrosoftDocs/azure-docs @.> Cc: George Guirguis @.>; Mention @.> Subject: Re: [MicrosoftDocs/azure-docs] Add resource group creation step for Event Grid (PR #128020)
[https://avatars.githubusercontent.com/u/56347952?s=20&v=4]ttorble left a comment (MicrosoftDocs/azure-docs#128020)https://github.com/MicrosoftDocs/azure-docs/pull/128020#issuecomment-3656440308
@george-guirguishttps://github.com/george-guirguis
Can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged" @MicrosoftDocs/public-repo-pr-review-teamhttps://github.com/orgs/MicrosoftDocs/teams/public-repo-pr-review-team
— Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/pull/128020#issuecomment-3656440308, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOGRWSUTDAIBZTEBATBVJX34B3MBVAVCNFSM6AAAAACO5POACOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMNJWGQ2DAMZQHA. You are receiving this because you were mentioned.Message ID: @.***>
#hold-off pending sign-off in PR conversation by author.
Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @george-guirguis