Azure Cloud Discovery – Custom Pattern Not Triggering

[DeventhiranS651]

Hi Team,

I recently started working on Azure Cloud resource discovery using patterns and encountered an issue with a custom pattern not triggering.

Background
For example, the Azure – Storage Volume (LP) resource type has an out-of-the-box extended pattern. When this resource type is removed from the Inclusion List table, the separate pattern for that resource type gets triggered during discovery, since the extended pattern is already available OOB.

Current Scenario:
For the example resource type Microsoft.Synapse/workspaces, there is:

I think No OOB extended pattern available

No entry for this resource type in the Inclusion List table

Because of this, I created a custom pattern similar to the Azure – Storage Volume (LP) pattern to handle this resource type.

Issue

During Azure discovery:

The custom pattern is not triggering

The resource type Microsoft.Synapse/workspaces is also not being processed by any pattern

Question
Could you please help clarify:

Are there additional configurations required for new Azure resource types so that the custom pattern gets triggered?

Does the resource type need to be registered somewhere (such as a specific mapping or configuration table) for pattern execution?

Are there any discovery framework limitations or prerequisites when creating patterns for new Azure resource types?

Any guidance or documentation references would be greatly appreciated.