Cloud database discovery is now done using Patterns.  The discovery for an Azure database may fail with the error:

Cloud request failed.


Status: 404

Server response:

Response: HTTP/1.1 404 Not Found [Cache-Control: no-cache, Pragma: no-cache, Content-Length: 253, Content-Type: application/json; charset=utf-8, Expires: -1, x-ms-request-id: westcentralus:<GUID>, x-ms-ratelimit-remaining-subscription-reads: 14997, x-ms-correlation-request-id: <GUID>, x-ms-routing-request-id: WESTEUROPE:20180620T122731Z:<GUID>, Strict-Transport-Security: max-age=31536000; includeSubDomains, X-Content-Type-Options: nosniff, Date: Wed, 20 Jun 2018 12:27:31 GMT, Connection: close]

The Issue is caused due to a problem with these patterns:

  • Azure - Database Convert JSON to XML
  • Azure DataBase

Steps to Reproduce

Not Applicable


This issue has been fixed. If you are able to upgrade, review the Fixed In or Intended Fix Version fields to determine whether any versions have a planned or permanent fix.

Related Problem: PRB1291451

Seen In

There is no data to report.

Intended Fix Version


Fixed In

Jakarta Patch 10
Kingston Patch 8

Safe Harbor Statement

This "Intended Fix Version" information is meant to outline ServiceNow's general product direction and should not be relied upon in making a purchasing decision. The information provided here is for information purposes only and may not be incorporated into any contract. It is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at ServiceNow's sole discretion.

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2018-10-25 02:25:03