Introducing Modular Cloud Discovery: Scan Only What You Need, When You Need It
IT environments are more heterogeneous than ever—public clouds, private infrastructure, hybrid assets, mobile devices… Managing this sprawl requires not just visibility but precision. That’s why we’re excited to announce a major enhancement in JDisc’s Cloud Discovery module: You can now run dedicated discovery jobs for each individual cloud service, such as AWS, Azure, or SOTI MobiControl, instead of scanning all cloud systems in one go.
🌐 Why We Changed the Cloud Discovery: More Control, Better Focus
Previously, JDisc ran a single unified cloud discovery job that queried all configured cloud providers in your setup. While this worked well for some users, others needed more control, especially in larger environments or testing scenarios.
With this new update:
- 🎯 You decide which cloud to scan—Azure, AWS, or SOTI—individually.
- ⏱️ Discovery jobs are faster, especially when isolating changes or debugging one provider.
- 🧪 Testing configurations become easier when onboarding a new cloud account.
Whether you want to scan Azure overnight and AWS during working hours, or test a SOTI MobiControl integration without touching production clouds—now you can.
🔧 What Changes with the Update of the Cloud Discovery?
To support this new flexibility, we’ve made a few important changes under the hood—and you’ll notice these right in your UI:
✅ Automatic Migration of Existing Cloud Configurations
When the update is installed:
- For any existing discovery job that had “Synchronize cloud services” checked a new cloud group will be automatically generated under the scope tree.
- The “Synchronize cloud services” checkbox is removed, since cloud accounts are now handled like this and will be handled with groups logic.
- You’ll see new Cloud Groups appear under the Scope tab in your jobs—one for each discovery job that you had enabled the old option.
🔍 New Workflow for Cloud Discovery
After the update, follow this simple three-step setup:
- Enable Your Cloud Accounts
Go to the Scope tab of any discovery job. You’ll find newly created cloud groups representing your configured cloud providers. Enable the specific accounts you want to scan from here. - Assign Cloud Groups to Discovery Jobs
Switch to the Groups tab in the discovery job settings. From there, enable the cloud group(s) you want to include in that specific job. This gives you precise control over what each job scans.
📈 What You’ll See as a Result
With this update, Cloud Discovery in JDisc becomes significantly more transparent, customizable, and scalable:
- 🧩 Modular Visibility: The Cloud tab is now decluttered. Cloud accounts are clearly associated with dedicated cloud groups, giving you a logical structure that mirrors how you think about your cloud environment.
- 🎛️ Precise Control: In each discovery job, you decide exactly which cloud groups are active. This means you can selectively scan AWS accounts in one job, Azure tenants in another, or isolate test environments without touching production data.
- ⚡ Faster Discoveries: By targeting only the accounts you need, you reduce runtime—making large-scale cloud inventories far more efficient.
- 🧹 Custom Group Management: Beyond automatic migration, you can create new cloud groups, delete outdated ones, and add or remove cloud accounts as needed. This provides maximum flexibility as your cloud footprint evolves.
With these improvements, your cloud discovery experience becomes cleaner, faster, and more aligned with your operational needs.
💡 Final Thoughts
This change empowers IT teams with granular control over their cloud discovery strategy.
Whether you’re securing mobile devices with SOTI, scaling workloads in AWS, or managing hybrid apps in Azure, JDisc now lets you discover what matters, when it matters.
Try it out today and let us know what else you’d like to see in our ever-expanding Cloud Discovery toolkit!
Stay in control,
Raphael Nikou
