Azure Subscription Event failed to create resource group 'undefined' - azure

Trying to deploy an Event Grid instance to harvest ARM events on my subscriptions. This instance is deployed on the subscription blade:
However, I get this error message when trying to deploy the event grid instance on the subscription.
I guess this is the resource group that has to be created in the background as the Event Grid instance cannot reside in a resource group to access events at the subscription level.
Cannot find any documentation on this error. Please advise.

Related

How to use Azure event grid to connect multiple storage accounts events to one function

We have a single subscription with multiple resource groups. We have multiple storage accounts in some of those resource groups. We want to watch for Blob changes in each of those storage accounts and trigger a shared function in one resource group (that is, the function exists in only one resource group).
We have successfully set up the function and an event grid subscription on a single storage account in a different resource group that successfully triggers the single central function.
Is there a convenient way to share the storage account subscriptions (via the event topic, for example)? Or do we need to set up an event subscription with topic for each storage account? In other words, if we have 5 storage accounts within a resource group, do we need 5 event subscription topics (one each)? We were somewhat hoping that there could be one subscription-topic most per resource group and each of those could/would have all the storage accounts that needed the event handler listed.
We can use advanced filtering that will monitor only storage account events. Event type can be Resource group. Here is the link that will help you to understand more on this.

Creation of System Topic failed while creating Event Subscription in Azure Maps

I keep getting the following error while creating Event Subscription for my Azure Maps Account.
Error:
Creation of System Topic has failed with error: System topic's location must match with location of the source resource /subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-a229d67dddf5/resourceGroups/rg-ets-new/providers/Microsoft.Maps/accounts/ets-maps-account. Event Subscription will not be created.
I get the same error if I add an Event Grid System Topic of Azure Maps Accounts Type in the same resource group the Maps Account is in. The resource group and the maps account both have the same region (West Centeral US) assigned to them.
What do you think is going wrong here? Any clues?
PS. The event subscriptions are working fine for other resources, Queues for example.
There seems to be an bug. We have reported it to Product teams. They are working on the fix. Meanwhile, there is an alternative to achieve the same.
We can successfully create an event grid topic with source events from an Azure Maps account by using Azure CLI, like in the below command. I have replaced any actual subscription details below with placeholders.
az eventgrid system-topic create --name topicName --location global --topic-type Microsoft.Maps.Accounts --source "/subscriptions/subscriptionName/resourceGroups/resourceGroupName/providers/Microsoft.Maps/accounts/mapAccountName" --resource-group "resourceGroupName"

Azure Event Grid subscription validations for logic app

I am creating event grid subscription with Custom delivery properties. I am setting the --delivery-attribute-mapping parameter when creating a subscription using the az eventgrid event-subscription create command.
Getting validation error. Validation token is not getting exchanged.
Thanks a lot in advance for your help and support

Azure DevOps - Releases Task is automatically set to "Scoped to resource group ''"

In our Azure Active Directory we have set up an App Registration for our service connection. The App Registration has Role Contributor for two different Resource Groups that in turn exists in two different subscriptions.
When the service connection is used it is automatically scoped to one resource group in one subscription anyway and this can't be changed.
Looking at Azure DevOps - Service connections we can see that even though the app has access to both subscriptions and resource groups it is in our case already mapped to a specific subscription and resource group.
Add a new service connection, choose Azure Resource Manager, Service Principal (automatic) and set it up against the other subscription or set up a new Management Group.

Move Azure SQL Managed Instance across subscription

I have two SQL managed instance in two different region(One in Australia East another one in Australia Southeast. They are in a Pay-As-You-Go subscription. Now I want to move those resources to a CSP subscription. Is it possible to move SQL managed instance across subscription?
Azure SQL managed instance supports the move operation: move to another resource group or another subscription. You can get this from this document: Move operation support for resources.
If you want to move the managed instance subscription, you need to operate on the resource group overview. Choose all the resource about managed instance.
For more details, please see this Azure tutorial: Move resources to new resource group or subscription:
Summary:
This article shows you how to move Azure resources to either another Azure subscription or another resource group under the same subscription. You can use the Azure portal, Azure PowerShell, Azure CLI, or the REST API to move resources.
Both the source group and the target group are locked during the move operation. Write and delete operations are blocked on the resource groups until the move completes. This lock means you can't add, update, or delete resources in the resource groups, but it doesn't mean the resources are frozen. For example, if you move a SQL Server and its database to a new resource group, an application that uses the database experiences no downtime. It can still read and write to the database.
Moving a resource only moves it to a new resource group. The move operation can't change the location of the resource. The new resource group may have a different location, but that doesn't change the location of the resource.
It also gives you many examples about how to move resource group or subscription:
By using Azure portal.
By using Azure PowerShell.
By using Azure CLI.
By using REST API.
Hope this helps.

Resources