Create Pull Request
| Date | Scan | Status | Result |
|---|---|---|---|
| 2026-01-14 00:00 | #250 | in_progress |
Biased
|
| 2026-01-13 00:00 | #246 | completed |
Biased
|
| 2026-01-11 00:00 | #240 | completed |
Biased
|
| 2026-01-10 00:00 | #237 | completed |
Biased
|
| 2026-01-09 00:34 | #234 | completed |
Biased
|
| 2026-01-08 00:53 | #231 | completed |
Biased
|
| 2026-01-06 18:15 | #225 | cancelled |
Clean
|
| 2025-08-17 00:01 | #83 | cancelled |
Clean
|
| 2025-07-13 21:37 | #48 | completed |
Biased
|
| 2025-07-12 23:44 | #41 | cancelled |
Biased
|
The resource group name is the service bus namespace name with **rg** appended.
2. Select **Copy** to copy the PowerShell script.
3. Right-click the shell console, and then select **Paste**.
It takes a few moments to create an event hub.
## Verify the deployment
To see the deployed service bus namespace, you can either open the resource group from the Azure portal, or use the following Azure PowerShell script. If the Cloud shell is still open, you don't need to copy/run the first and second lines of the following script.
Azure PowerShell is used to deploy the template in this tutorial. For other template deployment methods, see: * [By using the Azure portal](../azure-resource-manager/templates/deploy-portal.md). * [By using Azure CLI](../azure-resource-manager/templates/deploy-cli.md). * [By using REST API](../azure-resource-manager/templates/deploy-rest.md). ## Clean up resources When the Azure resources are no longer needed, clean up the resources you deployed by deleting the resource group. If the Cloud shell is still open, you don't need to copy/run the first and second lines of the following script.