@cbae: From what I saw in video, the basic, standard, and premium options will show up in the portal along with the current web and business choices.
My question is .... Given what sounds to be a really new pricing/performance model, how is a business partner expected to study their customers usage under current application logic, determine the peak to choose the proper new basic/standard/premium, then change the application logic to possibly auto-scale (given most customers usage will be peaks and valleys and not a steady set rate), then study their customers usage under the new application logic to come up with new pricing ..... and then finally have enough time remaining to inform their customers of pricing changes coming to them before the April 2015 date hits?
@Matthijs: If I'm understanding this correctly, the 3rd party developer builds the Windows Phone application and packages it in a XAP (not sure if it is signed or not signed at this point by the 3rd party developer). The XAP is then given to the enterprise where they can sign it and publish it in their private store.
What about enterprise customers who do not run a private store (i.e. small customers)? Can the 3rd party developer run a private store? This must be where you mention "give them access by an account or token". It seems like the customer's machines could only be enrolled in one store and in the case of a smaller customer it wouldn't make sense to have them NOT be enrolled in Microsoft's public store. This area is foggy.
What is the enterprise story for when a 3rd party developer produces a solution for an enterprise that includes a Windows Phone component? How does the 3rd party package and distribute the Windows Phone application such that it is private to the 3rd party and the 3rd party customers?