Azure Discovery

[PrithaB]

In Azure Discovery is it good to have all the subscriptions under a single schedule or is it better to have indivicual schedules for individual subscriptions? What are the Pros's and con's in each approach?

[Harish Bainsla]

Hi @PrithaB 

For Azure Discovery, having a single schedule for all subscriptions is generally better for simplicity and centralized management, but this approach can lead to very long discovery times, potentially missing critical updates, and making it harder to isolate issues. Using individual schedules for individual subscriptions provides greater flexibility, allows for different update frequencies to meet varying data freshness requirements (e.g., for security vs. non-critical data), and helps with troubleshooting, but it increases management overhead. 

Single Schedule

Pros:

• Easier to manage
• Centralized visibility
• Less configuration

Cons:

• Slower discovery time
• Can't meet different data freshness needs
• Harder to troubleshoot

---

Individual Schedules

Pros:

• Flexible and tailored updates
• Better data accuracy
• Easier issue isolation
• Scales well

Cons:

• More setup and monitoring
• Higher configuration effort

---

Recommendation:

Use individual schedules for critical or frequently changing subscriptions. Group similar subscriptions together. Use a single schedule only if all subscriptions have similar needs

also check below link

https://www.servicenow.com/community/itom-forum/is-it-possible-to-discovery-all-azure-subscriptions-...

if my answer helps you mark helpful and accept solution 

[Pratiksha]

Hi @PrithaB,

You can approach this either way, but it’s important to plan ahead. For instance, if you configure all subscriptions at once and also enable horizontal discovery after the cloud setup, it may take some time to complete. On the other hand, configuring each subscription separately creates overhead, since you’ll need to repeat the setup every time a new subscription is added.

Additionally, keep in mind that some organizations have policies requiring periodic key rotation, which you’ll need to factor into your approach.

Regards,
Pratiksha

[PrithaB]

Thanks @Pratiksha  and @Harish Bainsla for your responses, do you think Cloud Discovery Workspace can be a useful way of handling the errors in a single tenant approach? Does it help in isolating the errors and rectify them?