Forum Discussion
MicrosoftPrivate Offers - problems finding billing ID and failures accepting offers
Note: Please note that this discussion was carried over from a previous marketplace for partners community discussion. Original authorship has been removed.
_____________________________________________________________________________________________________________
We've been trying to us the Private Offers feature for our Marketplace offer and have hit a couple roadblocks in working with customers to extend the offers.
- Customers are having a real problem retrieving their Billing ID, which is required to extend the offer. Some can't find it, and more often than not, the customers we interact with do not have permission to view this information and do not know how to find the person in their organization who does. It would be great if there were an easier way to figure this information out that doesn't require a user with advanced permissions, and apparently more experience using Azure portal than any of our customers have.
- For the one customer who managed to provide their Billing ID, we extended the offer and they got an error trying to accept it: Accessing the page requires Azure Enterprise Agreement (EA) permissions for your organization's billing account. Please contact your EA admin to allow access. This permission level was not described in the documentation, and of course the customer does not know who the EA admin for their account is.
I like the feature, but we've had 0% success using it so far. Looking for some help here.
3 Replies
Also, I feel worth noting/sharing an additional area on this topic. If you are running across issues with accepting the private offer I have found it helpful to understand that a persons rights within Azure marketplace may only allow them to complete Step 1 (acceptance of the private offer). Often it could be the same person or someone else who has permissions to complete Step 2 (subscribe to the offer) which completes the private offer purchase. Hopefully this assists some others leveraging marketplace.
- justinroyal
Note: Please note that the response below was carried over from a previous marketplace for partners community discussion. Original authorship has been removed.
Thanks for discussion a few weeks back. I wanted to answer the questions for others also. Note, the question is specific to customer private offers (not CSP private offers) given customer private offers are created with the customer's billing account ID.
1. Billing account IDs can currently be found in the Azure portal, under Cost Management + Billing > Properties. Here are links to the relevant documentation: ISV documentation and customer documentation. We are also making updates to the Azure portal to make this billing account ID available as part of the subscription properties next month so it will be easier for customers to find the correct billing account ID.
2. Anyone in the customer's organization will be able to view the details of the private offer, but only those with the adequate permissions will be able to accept it. Here is the link to the relevant customer documentation and an ISV FAQ question on the topic. If the user does not have the appropriate permissions to accept the private offer, they will see a red dialog box at the top of the screen that will show them the users in their organization who do have the access and they can reach out to those users to either accept the private offer or provide the permissions to the user to accept.
Hope this helps!
- justinroyalNote: Please note that the response below was carried over from a previous marketplace for partners community discussion. Original authorship has been removed. On point 1, could it be the customer only has CSP billed Azure subscriptions? Typically the customer doesn't have a billing ID in this case. We have had to talk customers through creating an additional PAYG Azure sub in order to consume our app. We've given up on private offers to customers in part because of this. We now have a set of private plans on the offer. With private plans, you target the customer's Azure tenant ID, which is much easier to find (and can be done programmatically).
