You're on the right track with your approach to organizing multiple clusters and scan jobs in Microsoft Purview. Here's some clarity around your questions:
Creating Multiple Clusters
Yes, creating multiple clusters in Purview is absolutely valid and often recommended, especially when separating Test and Production environments. This makes it easier to manage and organize scans across different datasets or environments.
Content Scan Jobs
What you're noticing is expected behavior:
Microsoft Purview allows only one active scan job per data source or integration runtime (IR) at a time.
If a scan is already running (or hasn't been fully completed or canceled), other scan jobs, especially those targeting the same resource via the same IR — may not show the Scan option until the current one finishes.
What You Can Do
Check if an earlier scan is still in progress or queued, it will block new scans from starting.
Consider using separate integration runtimes for Test and Prod clusters if you need to run scans in parallel.
For more details, please refer: https://learn.microsoft.com/en-us/purview/deploy-scanner-configure-install?tabs=azure-portal-only#optimize-scanner-performance
I hope this information helps. Please do let us know if you have any further queries.
If this answers your query, do click Accept Answer
and Yes
for was this answer helpful. And, if you have any further query do let us know. Thank you.