Search Engine: Elastic

Article ID: 131409, created on Sep 3, 2017, last review on Jul 14, 2018

  • Applies to:
  • Operations Automation 7.0
  • Operations Automation 6.0


On an attempt to place a new order for Azure CSP, checking the subdomain * works improperly: it periodically reports domains as free, despite those are in use.


Used version of the Azure CSP package uses external Yahoo! service to check the subdomain availability in Microsoft. Due to some connectivtity issue, the query run from Yahoo! to Microsoft returns a 400 Bad Request error, which is incorrectly treated by OA.


It is recommended to upgrade Azure CSP to the version 4.5.2 or later. The latest version of the package uses new PC API which allows to check the subdomain directly in Microsoft.

In order to resolve the issue on older versions of Azure CSP, re-apply the script.js file according to the OA and application version per this article.

0871c0b47b3b86ae3b1af4c2942cd0ce caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 5356b422f65bdad1c3e9edca5d74a1ae 1941880841f714e458ae4dc3d9f3062d 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF