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

Dinesh Kanna P 0 Reputation points

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 ---

  1. The WNS/MPNS Push Notifications page under Product Management does not load properly.
  2. The Client Secret has been generated via the App Registration portal, but WNS credential configuration is still not accessible.
  3. 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.
  4. 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 ---

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

--- REQUEST ---

Could you please:

  1. Refresh / re-provision the WNS backend registration for the above Package SID
  2. Confirm whether the MSA App ID (fc115825-e519-4ec8-bbcd-dad074cea454) is correctly linked to the Store Package SID
  3. 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

  1. Varun Burra 5 Reputation points • Microsoft External Staff • Moderator

    Hello @Dinesh Kanna P ,

    Thank you for reaching us regarding the issue.

    This issue appears to be caused by incomplete WNS backend provisioning for your Store app in Microsoft Partner Center. For WNS to work, the Package SID from Partner Center and the Client Secret must come from the same app registration that is created and linked through the WNS/MPNS page in Partner Center. If the Push Notifications page is not loading, the WNS registration for your Package SID may not have been fully initialized on Microsoft’s backend, which also explains why Microsoft Azure Notification Hubs shows errors like “this._wnsCredential is not a function.”

    Please verify in Partner Center that your app identity (Package SID, Package Family Name, and Publisher) matches the package used in your app. Then, sign in with the same Microsoft account that owns the Store listing, clear browser cache / use InPrivate mode, and go to Product Management → Push notifications. If the page still does not load, this is not something that can be fixed from the Azure portal or app side.

    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.

  2. Varun Burra 5 Reputation points • Microsoft External Staff • Moderator

    Hello @Dinesh Kanna P ,

    We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

  3. Dinesh Kanna P 0 Reputation points

    I have followed the steps but no improvements in wns

Sign in to comment

1 answer

  1. AI answer

    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:

    1. 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.
    2. 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.
    3. 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:

    AI-generated content may be incorrect. Read our transparency notes for more information.
Sign in to answer

Your answer