Steps on ServiceNow Azure Cloud Discovery Setup: From Credentials to CI Detection
This guide walks you through the discovery of ServiceNow Azure Cloud Discovery essential setup steps—from credential creation to workspace configuration—empowering you to maximize the value of ServiceNow Azure Cloud Discovery for efficient cloud governance and infrastructure management.
ServiceNow Azure Cloud Discovery prerequisite:
- Get Cloud Service Account
- Get Azure Service Principal Credential
- Ensure mid server is setup and ready to use
- Access Cloud Discovery Workspace to manage schedules.
ServiceNow Azure Cloud Discovery Credentials Setup:
To begin cloud discovery, obtain a credential from the Azure team that works across all subscriptions/accounts.
To configure the acquired creds on ServiceNow follow the below steps:
- Navigate to: All > Discovery > Credentials > New
- Select: Type = Azure Service Principal
- Set up the credential as shown in the reference image.
Cloud Service Accounts
Let’s say we have 12 environments and their Account ID/Subscription ID in our Azure cloud:
- Request corresponding 12 cloud service accounts from the Azure team.
- Create them at: All > Cloud Provisioning and Governance > Service Accounts
ServiceNow Azure Cloud Discovery Workspace:
- Go to: Workspace > Cloud Discovery Workspace
- Select: Cloud Discovery (as shown in the image)
Creating ServiceNow Azure Cloud Discovery Schedule
- Click +New discovery schedule.
- It is strongly recommended to use the workspace UI instead of the native UI:
All > Discovery Schedule > New
Follow these steps and images:
- Choose the provider > Select the Service Account.
- Click Test Account.
○ If credentials are correct, a green success message appears.
○ If it fails, contact the Azure team.
Data Center Configuration
- Select All Data Centers > Click Refresh Data Centers occasionally (not required every
time).
- Toggle on: Discover Virtual Machines
Finalizing the ServiceNow Azure Cloud Discovery Schedule:
- Configure the schedule as needed > Click Finish and Run.
This process is known as API-based discovery
IP-Based Discovery (VM Schedule)
After creating the API-based schedule:
- A secondary schedule with the same name with the suffix VM Schedule is automatically
created. Please refer to the image below.
- This is used for IP-based (MID server-based) discovery
Steps:
- Open the VM Schedule.
- Attach:
○ MID Server or MID Server Cluster
○ Discovery Range Sets (Received from Azure team)
○ Other required configurations as shown in the image
- Use the DiscoverNow form link to trigger IP-based discovery.
The ideal location to check discovered CIs is within the ServiceNow Azure Cloud Discovery workspace.
If you find the article to be useful or effective for your knowledge Kindly Consider Marking the article HELPFUL and BOOKMARK if for your future use...
<<< Top Articles >>>
- ServiceNow Integration with Splunk
- LDAP Integration with ServiceNow
- ServiceNow Integration with Veeam
- Handling ServiceNow flow errors with a flow
- Show parent child incident relationships - display in field message
- ServiceNow SSO Logout Error (redirects to logout page) – Reason, Fixes and Cause.
- Multi Row Variable set ServiceNow MRVS - Creating - Scripting - Example - Limits
- ServiceNow Integration with MAC vendor - Get Mac vendor for the given MAC Address.
- How to find Log4j vulnerable severs in ServiceNow Using CMDB Query Builder (SecOps)
- How to Cancel a Long-Running Transaction ServiceNow
- Hidden Features for System Administrators
- Servicenow RPA - Understanding Attended / Unattended / Skilled Automation Bots
MF Sohail Khilji | ServiceNow Developer / Consultant.
Connect On LinkedIn > https://www.linkedin.com/in/mf-sohail-khilji/
