Invalid WNS credentials error when setting up new notification hub

Perpetua Technologies LLC 21

I am running into problems while configuring the WNS settings for my new Notification hub. On step #3 of "Configure WNS settings for the hub" I'm getting an error:

{"error":{"code":"BadRequest","message":"Invalid WNS credentials."}}

I'm attempting to follow the instructions at this site:

https://learn.microsoft.com/en-us/azure/notification-hubs/notification-hubs-windows-store-dotnet-get-started-wns-push-notification

Other posted resolutions for this problem didn't resolve my issue.

Here are screenshots of the process so far:

Step 3 of "Create an app in Windows Store":

Step 3 of Create an app in Windows Store Step 5 of "Create an app in Windows Store":

Step 5 of Create an app in Windows Store

Step 6 of "Create an app in Windows Store":

Step 6 of Create an app in Windows Store

Step 5d of "Create a Notification Hub":

Step 5d of Create a Notification Hub

Step 3 of "Configure WNS settings for the hub": Step 3 of Configure WNS settings for the hub

Copilot suggestions didn't help.

Laxman Reddy Revuri 2,390 Reputation points Microsoft Vendor

2025-02-12T19:23:23.7233333+00:00

Hi @Perpetua Technologies LLC
Thanks for the question and using MS Q&A platform
Based on error messages and screenshot, it looks like you're experiencing an issue with invalid WNS (Windows Notification Service) credentials while setting up your Azure Notification Hub.
1.The Package SID and Security Key must come from the Windows Dev Center. If the credentials don’t match the registered app, WNS authentication will fail.

2.Sometimes, old or incorrect credentials cause issues. Copy-pasting directly from the Windows Dev Center ensures accuracy.

3.Removing extra spaces helps avoid formatting issues.

If credentials have expired or were changed, old keys won’t work. Regenerating ensures fresh, valid credentials.

4.If an account lacks permission, it might not update credentials properly. Ensuring correct RBAC (Role-Based Access Control) settings is important.

5.Go to Activity Logs in Azure Notification Hub to see exact errors.

6.If credentials were updated, the app may need to re-register with WNS.

7.The package name in Package.appxmanifest must match the registered app.

Perpetua Technologies LLC 21

Laxman Reddy Revuri,

Thanks for the canned response. Here are my responses to your numbered items.

When you say "Windows Dev Center" I'm assuming you mean the "Partner Center", since visiting developer.microsoft.com doesn't give me the option to log in, only an option to go to the partner center (see image). As you can see from the screenshots in my original post, the Package SID matches, and the Security Key that came from Azure (as per the instructions) are also a match. I tried with 2 different newly created secrets and both failed.
There is only one app in question, so no old credentials to copy. As per the screenshots in my original post, you can see that the credentials were copied exactly, not typed in by hand.
No extra spaces where present when I made my attempts, and I was sure of that each time I tried. Credentials were never expired or changed; it's a brand new app registration.
I'm logged in as the owner of the company and I have one roll: Global Administrator (see image). I assume this should handle the case I need. If this is not sufficient, please come forward with the roll(s) I need to assign to make this request.

The JSON Activity log for one of the repeated failed attempts is as follows:

   {
       "authorization": {
           "action": "Microsoft.NotificationHubs/namespaces/notificationHubs/write",
           "scope": "/subscriptions/4234d16d-04e6-4374-bd61-78ebf1f896e4/resourceGroups/EnRoutePro4/providers/Microsoft.NotificationHubs/namespaces/EnRoutePro4/notificationHubs/ERP4Hub"
       },
       "caller": "******@gmail.com",
       "channels": "Operation",
       "claims": {
           "aud": "https://management.core.windows.net/",
           "iss": "https://sts.windows.net/7462dec3-1a01-48dc-94d2-e117906d1489/",
           "iat": "1739377631",
           "nbf": "1739377631",
           "exp": "1739382888",
           "http://schemas.microsoft.com/claims/authnclassreference": "1",
           "aio": "AbQAS/8ZAAAAy+pw2wGZhkAtopExzVBbBfNaTqLxOxcBteM3sJK7sBBHzoDJGiPZ7ra+cjOZh/gHFlDmggb6N/5nJxGFsxobJsJCmsC2Zp7uSbEtVlBPML3mrGOdgT7wHKOk0S4OV8t8zFREoGoEkkjXe9IVbgynQxbCDPJbLtBUTGCDFakFzcmM7mAoNaAoxuPbk+Zknx4z5Y3OfZ+l/V1Es3vUMMgj5y+T0uNVK8MZf5OfGndnJUo=",
           "altsecid": "1:live.com:0003BFFD0814D4BE",
           "http://schemas.microsoft.com/claims/authnmethodsreferences": "pwd,mfa",
           "appid": "c44b4083-3bb0-49c1-b47d-974e53cbdf3c",
           "appidacr": "2",
           "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress": "******@gmail.com",
           "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname": "Technologies LLC",
           "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname": "Perpetua",
           "groups": "174f98cd-03e1-4edd-b495-d9ab7174a702",
           "http://schemas.microsoft.com/identity/claims/identityprovider": "live.com",
           "idtyp": "user",
           "ipaddr": "38.77.241.58",
           "name": "Perpetua Technologies LLC",
           "http://schemas.microsoft.com/identity/claims/objectidentifier": "d4c150cc-9fb0-4238-b7c5-ae7ef2fe5029",
           "puid": "1003200089B23049",
           "rh": "1.AUYAw95idAEa3EiU0uEXkG0UiUZIf3kAutdPukPawfj2MBPxACJGAA.",
           "http://schemas.microsoft.com/identity/claims/scope": "user_impersonation",
           "sid": "00201309-3a07-ab98-2f8e-4291d385638f",
           "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier": "pmzJmmfluC8qEusheS65AOSospDtL6VyTAuJAt2XP-I",
           "http://schemas.microsoft.com/identity/claims/tenantid": "7462dec3-1a01-48dc-94d2-e117906d1489",
           "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name": "live.com#******@gmail.com",
           "uti": "dKTOphBly0qtnVBcx60MAA",
           "ver": "1.0",
           "wids": "62e90394-69f5-4237-9190-012177145e10",
           "xms_edov": "true",
           "xms_idrel": "1 2",
           "xms_tcdt": "1574294909"
       },
       "correlationId": "8d12c625-297c-4d47-8680-3451fc2ecce3",
       "description": "",
       "eventDataId": "d5fd2244-e85b-4f8e-a8fb-1e662e25b4f5",
       "eventName": {
           "value": "EndRequest",
           "localizedValue": "End request"
       },
       "category": {
           "value": "Administrative",
           "localizedValue": "Administrative"
       },
       "eventTimestamp": "2025-02-12T16:42:18.6795327Z",
       "id": "/subscriptions/4234d16d-04e6-4374-bd61-78ebf1f896e4/resourceGroups/EnRoutePro4/providers/Microsoft.NotificationHubs/namespaces/EnRoutePro4/notificationHubs/ERP4Hub/events/d5fd2244-e85b-4f8e-a8fb-1e662e25b4f5/ticks/638749753386795327",
       "level": "Error",
       "operationId": "8d12c625-297c-4d47-8680-3451fc2ecce3",
       "operationName": {
           "value": "Microsoft.NotificationHubs/namespaces/notificationHubs/write",
           "localizedValue": "Create or Update Notification Hub"
       },
       "resourceGroupName": "EnRoutePro4",
       "resourceProviderName": {
           "value": "Microsoft.NotificationHubs",
           "localizedValue": "Microsoft.NotificationHubs"
       },
       "resourceType": {
           "value": "Microsoft.NotificationHubs/namespaces/notificationHubs",
           "localizedValue": "Microsoft.NotificationHubs/namespaces/notificationHubs"
       },
       "resourceId": "/subscriptions/4234d16d-04e6-4374-bd61-78ebf1f896e4/resourceGroups/EnRoutePro4/providers/Microsoft.NotificationHubs/namespaces/EnRoutePro4/notificationHubs/ERP4Hub",
       "status": {
           "value": "Failed",
           "localizedValue": "Failed"
       },
       "subStatus": {
           "value": "BadRequest",
           "localizedValue": "Bad Request (HTTP Status Code: 400)"
       },
       "submissionTimestamp": "2025-02-12T16:44:12Z",
       "subscriptionId": "4234d16d-04e6-4374-bd61-78ebf1f896e4",
       "tenantId": "7462dec3-1a01-48dc-94d2-e117906d1489",
       "properties": {
           "statusCode": "BadRequest",
           "serviceRequestId": null,
           "statusMessage": "{\"error\":{\"code\":\"BadRequest\",\"message\":\"Invalid WNS credentials.\"}}",
           "eventCategory": "Administrative",
           "entity": "/subscriptions/4234d16d-04e6-4374-bd61-78ebf1f896e4/resourceGroups/EnRoutePro4/providers/Microsoft.NotificationHubs/namespaces/EnRoutePro4/notificationHubs/ERP4Hub",
           "message": "Microsoft.NotificationHubs/namespaces/notificationHubs/write",
           "hierarchy": "4234d16d-04e6-4374-bd61-78ebf1f896e4"
       },
       "relatedEvents": []
   }

Credentials where never updated, as this is a brand new app registration.
As you may tell from the original walkthrough I'm following, the problem I'm running into happens before needing to do anything within the application itself, so I'm not even to the stage where I'm editing the Package.appxmanifest file.

Please, if there's something I'm missing here let me know.

Thanks.

Accepted answer

SnehaAgrawal-MSFT 22,261 Reputation points

2025-02-13T10:37:11.06+00:00

@Perpetua Technologies LLC

Could you please Confirm Package SID should be in the format: ms-app://S-x-xx-x-xxxxxxxx..

And not in the format S-x-xx-x-xxxxxxxxxxxxxx.... (this is how it looks in partner center portal)

As mentioned in the doc- https://learn.microsoft.com/en-us/azure/notification-hubs/notification-hubs-windows-store-dotnet-get-started-wns-push-notification#configure-wns-settings-for-the-hub

Let me know.
Please sign in to rate this answer.

1 person found this answer helpful.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

1 additional answer

Perpetua Technologies LLC 21 Reputation points

2025-02-13T16:05:36.0166667+00:00

Laxman Reddy Revuri,The "ms-app://" portion of the Package SID was indeed the issue I was seeing. Thank you for catching that! I was able to save the properties of the new hub with no errors.

Thanks.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Invalid WNS credentials error when setting up new notification hub

1 additional answer

Your answer