question

Dev-5728 avatar image
0 Votes"
Dev-5728 asked RoyLi-MSFT edited

Providing "Restricted Capabilities" explanation via Microsoft Store submission API

It appears that there is currently no (documented) way to provide the “Restricted Capabilities” explanation via the Microsoft Store submission API?

For a Desktop Bridge app packaged as an MSIX, the “runFullTrust” restricted capability is always required, per: https://docs.microsoft.com/en-us/windows/uwp/packaging/app-capability-declarations#restricted-capabilities

Windows Developer support has informed that the “Restricted Capabilities” explanation field may be required periodically - even if the Restricted Capabilities used by an app submission have not been changed in subsequent app submission updates.

With the apparent lack of an ability to provide this field via the Microsoft Store submission API, this would seem to mean that it is not possible to reliably use the Microsoft Store submission API for updating Desktop Bridge applications.

This is a real bummer, especially since the use of - and explanation for - the “runFullTrust” restricted capability doesn’t change for Desktop Bridge apps.

Is there an undocumented way to provide the “Restricted Capabilities” explanation field via the Microsoft Store submission API, or could support for this field please be added? (Simply being able to provide this field to the API would seemingly solve this issue, and ensure the information is present for reviewers when required.)

(Note: The Microsoft Store submission API does support a “notesForCertification” field, but this appears to be distinct from the “Restricted Capabilities explanation / justification” field.)


partner-center-general
· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

It appears that there is currently no (documented) way to provide the “Restricted Capabilities” explanation via the Microsoft Store submission API?

First of all, it is recommended to submit your app in the Partner Center manually.

For your scenario, you could also try to open a free support ticket here: Contact Us. Go to Contact us, find Non-Technical Support - Dashboard and choose CHAT NOW or
SUBMIT AN INCIDENT
. Then you could talk to the store team directly.

0 Votes 0 ·

First of all, it is recommended to submit your app in the Partner Center manually.

The documentation for StoreBroker:

This module is actively used within Microsoft as the primary way that our first-party application teams submit flight updates and public submission updates to the Windows Store, and is now available to the general developer community to leverage as well.

as well as the documentation for the API itself:

This API is useful if your account manages many apps or add-ons, and you want to automate and optimize the submission process for these assets.

Would seem to give the opposite impression?

At the moment the Microsoft Store is the sole exception to an otherwise automated release process - and only because it apparently(?) occasionally requires submission of a non-changing textual explanation which the API doesn't provide a field for (but which Partner Center does).

For your scenario, you could also try to open a free support ticket here [...]

Alas, I've already done that and they suggested I post here. Is there another option that's recommended?


0 Votes 0 ·

Alas, I've already done that and they suggested I post here. Is there another option that's recommended?

Another way is to submit feedback in the Feedback Hub. But if you have already opened a support ticket about this, please contact the store team via that channel. Thank you for your patience.

0 Votes 0 ·

0 Answers