Error while performing Azure Cloud Discovery - 443 login microsoftonline
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-24-2026 11:59 AM
Hello All,
I'm trying to schedule cloud discovery for one account for which credentials are already configured and receiving below error, If anyone is familiar with this do let me know the solution
Exception occurred while executing operation Cloud REST - add response to context. Custom operation Failed to run script due to the following error: JAVASCRIPT_CODE_FAILURE: com.snc.sw.exception.CommandFailureException: Failed to execute cloud request. Reason: HttpHostConnectException:Connect to login.microsoftonline.com:443 [login.microsoftonline.com/20.190.190.131, login.microsoftonline.com/20.190.190.193, login.microsoftonline.com/40.126.62.131, login.microsoftonline.com/20.190.190.196, login.microsoftonline.com/40.126.62.132, login.microsoftonline.com/40.126.62.129, login.microsoftonline.com/20.190.190.129, login.microsoftonline.com/20.190.190.194] failed: Connection timed out: getsockopt (script_include:AzureApiCommand; line 69)
HttpHostConnectException:Connect to login.microsoftonline.com:443 login.microsoftonline.com
Thank you !
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards
Akshay Kamble (SD_Akshay)
ServiceNow Developer
LinkedIn: https://www.linkedin.com/in/akshay-kamble-1504/
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-24-2026 08:05 PM
Hi @SD_Akshay
Check these possible causes :
- Ensure the MID Server can access login.microsoftonline.com:443 and management.azure.com:443 outbound.
- Validate that the Service Principal credentials (Client ID, Secret) are not expired and have correct permissions in Azure.
- Verify the token URL format is correct, typically: https://login.microsoftonline.com/{tenant_id}/oauth2/v2.0/token.
- Ensure necessary certificates are installed on the MID Server machine.
- Re-validating the MID Server in some cases solve the issue
Refer:
https://www.servicenow.com/community/itom-forum/azure-cloud-discovery/m-p/3428560
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Monday
Hi Tanushree,
Apologies for not responding, the issue was with MID Server configurations which previous team had done, the MID was in different VLAN is what they confirmed afterwards.
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards
Akshay Kamble (SD_Akshay)
ServiceNow Developer
LinkedIn: https://www.linkedin.com/in/akshay-kamble-1504/
****************************************************************************************************************
