Search Engine: Elastic

Article ID: 129663, created on Oct 23, 2016, last review on Oct 23, 2016

  • Applies to:
  • Operations Automation 6.0


Office365 Provisioning Subscription task fails:

Partner with Id '1234' is not valid for Offer xxxxxxxx-xxxx-xxxx

Upon subscription provisioning, Office365 application sends the following CREST API request:

x-ms-tracking-id: b915574e-4724-4c12-8b5d-157b3fb4e665

It also passes advisor_partner_id parameter which is configured as MPN_ID attribute for reseller account on the Billing side. The request format is valid, according to the CREST API specification.

An error occurs on the Microsoft side, the response of the request is equal to the OA task output:

Response received on thread default task-27
< 403
< api-version: 2015-03-31
{"object_type":"Error","code":"OMS_6081","error_code":"AccessDenied","message":"Partner with Id '713621' is not valid for Offer '5C9FD4CC-EDCE-44A8-8E91-07DF09744609'"}


Reseller with specific advisor_partner_id in question is incompatible with the exact offer on the Microsoft side for some reason.


Please, contact Microsoft support in order to resolve the issue.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF