WNS Push Notification Page Not Loading — Backend Provisioning Issue | Store ID: 9P88Q1MP20V4

Question

WNS Push Notification Page Not Loading — Backend Provisioning Issue | Store ID: 9P88Q1MP20V4

Dinesh Kanna P 0

Hi Microsoft Partner Center Support Team,

I am writing to report a WNS (Windows Push Notification Service) backend provisioning issue for my app registered on Microsoft Partner Center.

Despite successfully creating the app, reserving the package identity, and generating a Client Secret via the App Registration portal, the WNS Push Notifications page in Partner Center is not loading and WNS credentials cannot be configured.

--- APP DETAILS ---

App Name: desktop authenticator

Store ID: 9P88Q1MP20V4

Store URL: https://apps.microsoft.com/detail/9P88Q1MP20V4

Package Identity Name: Dineshkanna.desktopauthenticator

Publisher: CN=7575652E-8E7F-4F77-9B5B-2E82844DF58F

Publisher Display Name: Dinesh kanna

Package Family Name: Dineshkanna.desktopauthenticator_bb0fygvrvh2qr

Package SID: S-1-15-2-799718017-168720558-1825898705-1012579215-1047398943-1587462034-1523153169

MSA App ID: fc115825-e519-4ec8-bbcd-dad074cea454

--- ISSUE DESCRIPTION ---

The WNS/MPNS Push Notifications page under Product Management does not load properly.
The Client Secret has been generated via the App Registration portal, but WNS credential configuration is still not accessible.
The Azure Notification Hub (Windows WNS blade) throws error: "this._wnsCredential is not a function" — indicating the WNS registration is not provisioned on the backend.
This appears to be a backend provisioning issue where the WNS registration for this Package SID has not been properly initialized on Microsoft's side.

--- WHAT I HAVE TRIED ---

Created app in Partner Center with personal Microsoft account
Generated Client Secret via apps.dev.microsoft.com
Attempted to configure WNS in Azure Notification Hub using Package SID and Client Secret
Tried refreshing and re-accessing the WNS/MPNS page multiple times
Created a new app registration — same issue persists

--- REQUEST ---

Could you please:

Refresh / re-provision the WNS backend registration for the above Package SID
Confirm whether the MSA App ID (fc115825-e519-4ec8-bbcd-dad074cea454) is correctly linked to the Store Package SID
Advise if any additional steps are needed on my end to resolve this

Thank you for your support. Please let me know if you need any additional information.

Regards,

Dinesh kanna

Varun Burra 0 Reputation points Microsoft External Staff Moderator

2026-04-07T17:03:17.53+00:00
Hello @Dinesh Kanna P Thank you for reaching us regarding the issue.

From the information provided, it seems the WNS registration linked to your app’s Package SID hasn’t been fully set up in Microsoft Partner Center. When backend provisioning is incomplete, the Push Notifications page may not load, and Azure Notification Hubs might show errors like “this._wnsCredential is not a function” because valid credentials for Windows Push Notification Services aren’t available.

For Windows Store apps, the Package SID created in Partner Center should be connected to an app registration with a Client Secret. These are used to authenticate with Windows Push Notification Services through Azure Notification Hubs. Since this configuration is handled on Microsoft’s backend, it usually can’t be fixed from the Azure portal or app side. The best solution is to ask Microsoft support to verify or refresh the WNS registration in Partner Center so the Push Notifications page works and credentials are accessible.

Please contact Microsoft support to check and refresh the WNS provisioning for Package SID S-1-15-2-799718017-168720558-1825898705-1012579215-1047398943-1587462034-1523153169. After the backend refresh, the Push Notifications page should load and let you configure or get the credentials needed for Windows Push Notification Services.

Make sure the MSA App ID (fc115825-e519-4ec8-bbcd-dad074cea454) is properly linked to the Store app identity and Package SID in Partner Center. If not, the backend team may need to rebind the registration for proper authentication.

After the refresh, sign in to Partner Center with the Microsoft account that owns the Store listing and app registration. Clear your browser cache or use a private window, then go to Product Management → Push Notifications and check if the WNS credentials section loads. Once available, re-enter the Package SID and Client Secret in Azure Notification Hubs and save the settings.

Reference:

https://learn.microsoft.com/azure/notification-hubs/configure-notification-hub-portal-pns-settings#windows-push-notification-service

https://learn.microsoft.com/windows/apps/develop/notifications/push-notifications/troubleshoot-notifications

If you need more help, please let us know.

If this information was helpful, please consider upvoting so it can assist others in the community.

1 answer

Your answer

Answer 1

For this scenario, the behavior indicates a backend provisioning issue with WNS credentials for the app in Partner Center, similar to other cases where WNS does not recognize or expose valid credentials even though the app is correctly registered.

This cannot be fixed from the app or Azure Notification Hubs side. The required action is to have Partner Center support verify and, if necessary, refresh or re-provision the WNS registration for the Store app ID and Package SID.

Recommended steps:

Open a support request with Microsoft Partner Center
- Use the Partner Center support channel described here: https://learn.microsoft.com/en-us/partner-center/support/schedule-support-appointment (from the referenced Q&A).
- In the ticket, include:
  - Store ID: 9P88Q1MP20V4
  - Store Product URL (optional for context)
  - Package Family Name
  - Package SID
  - MSA App ID
  - Screenshots or description of:
    - WNS/MPNS page not loading in Partner Center
    - Azure Notification Hub error: this._wnsCredential is not a function
    - Any HTTP errors or console errors when loading the WNS/MPNS page.
Ask Partner Center support to:
- Validate that the Package SID is correctly registered with WNS.
- Refresh or re-provision the WNS registration for the Package SID.
- Confirm that the Partner Center app registration and the MSA app registration are correctly linked for WNS.
After support confirms the backend is fixed:
- Reopen the WNS/MPNS page in Partner Center and verify that WNS credentials (Package SID, client secret) are visible and configurable.
- Reconfigure Azure Notification Hub WNS credentials using:
  - package-sid = the Package SID from Partner Center.
  - secret-key = the client secret from the app registration.
- If using Azure CLI, update the hub with:
  - az notification-hub credential wns update --resource-group <rg> --namespace-name <ns> --notification-hub-name <hub> --package-sid <sid> --secret-key <secret>.

If, after Partner Center re-provisions WNS, the OAuth token request or WNS configuration still fails, provide Partner Center and/or Azure support with the exact request body, timestamps, and error messages so they can further validate the WNS backend registration, as done in similar cases.

References:

Share via

WNS Push Notification Page Not Loading — Backend Provisioning Issue | Store ID: 9P88Q1MP20V4

1 answer

Your answer