Search Engine: Elastic

Article ID: 112601, created on Oct 22, 2011, last review on Mar 1, 2015

  • Applies to:
  • Operations Automation 5.x


A customer delegates the domain "" to Microsoft in their subscription with Office 365 services. After that, the customer wants to create a user in POA CCP and assign a Microsoft Office 365 offer (subscription) to the user.

However, the customer cannot add a service user with Office 365 service in POA CCP because the domain is not marked as "verified" in POA.

At the same time, the domain is marked as "verified" in Microsoft; this may be checked in the Microsoft Online Portal.

Domain verification on MOSI Gateway Host fails with diagnostics like this:
2011-10-11 13:15:29,117 [   5] DEBUG mosi-clients: >>> VerifyDomain({"DomainName":"","ExtensionData":null,
2011-10-11 13:15:29,398 [   5] ERROR mosi-clients: <<< VerifyDomain by exception
DomainNotVerifiedFault (Fault Detail is equal to
2011-10-11 13:15:29,398 [   5] DEBUG db          : NEXT VERIFICATION:10/11/2011 6:17:29 PM
2011-10-11 13:15:29,398 [   5] DEBUG entity      : vrf save{"custId":"e86fb5eb-565a-45ac-a242-41d0890ec508",
2011-10-11 13:15:29,414 [   5] DEBUG flow        : Verification of failed


A possible reason for the problem is incorrect implementation of MOSI Gateway software -- It assumes that the customer has at least one subscription (offer) in Microsoft. During the domain verification process, MOSI Gateway tries to get the SubscriptionId from the MOSI database and specify it in the IDomainManagement method's call to the Microsoft Office 365 server.

If a customer, for any reason, has no subscription yet, then obtaining the SubscriptionId fails and the domain cannot be verified. According to MOSI SDK, the SubscriptionId parameter is optional for all methods of the IDomainManagement interface and may be omitted.


The problem is resolved in Office 365 1.3. Update MOSI Gateway software to Office 365 1.3 or a newer version.

5356b422f65bdad1c3e9edca5d74a1ae 2554725ed606193dd9bbce21365bed4e caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF