How to link a currently existing Azure app with a newly register microsoft dev center application to gain access to wns services.

Question

How to link a currently existing Azure app with a newly register microsoft dev center application to gain access to wns services.

Bror Vedeld 0

Hi,
I am trying to register for push notifications using the sample provided at the official windows github.
I could not get access to the company infrastructure and needed to register my own.

In order to add wns to my azure subscription i need a SID and a secret key from the Associated microsoft developer application. I found the SID but not the secret key. The only hint i can find in the documentation is that "you will recieve it when you register the application" but it isn't under product information, where i found the SID.

I can't figure out how to link the azure app i have created with the app i registered at microsoft developer center, in order to source the secret key. Any help or direction to relevant documentation would be greatly appreciated.
Regards

Bhargavi Naragani 7,940 Reputation points Microsoft External Staff Moderator

2025-02-13T06:38:33.75+00:00

Hi @Bror Vedeld,
Welcome to the Microsoft Q&A Platform!

To associate your current Azure app with the newly registered Microsoft Developer Center application that allows access to Windows Notification Services (WNS), you should make sure that you have both the Package Security Identifier (SID) and the secret key of the Microsoft Developer application.

The secret key is created when you generate a client secret for your app registration within the Azure portal. You can accomplish this by going to the "Certificates & secrets" blade of your Azure app registration and clicking on "New client secret." Be certain to copy the secret key the moment it has been created because it will no longer be visible.

Once you have received the secret key, you can use both the SID and the secret key to authenticate your cloud service with WNS. Make sure that your Azure app registration is correctly set up to utilize the same Package Family Name (PFN) as your Microsoft Developer Center application.

If your app is packaged, you might need to map your app's PFN to its Azure AppId. For packaged Win32 apps, you can request a mapping by email to Microsoft.

Reference:
Quickstart: Push notifications in the Windows App SDK

Windows Push Notification Services (WNS) overview

Tutorial: Send notifications to Universal Windows Platform apps using Azure Notification Hubs

Hope the above provided information help in better understanding and help you resolve the issue, if you have any further concerns or queries, please feel free to reach out to us.
If the answer is helpful, kindly Upvote it.
Bror Vedeld 0 Reputation points

2025-02-13T10:53:55.6566667+00:00

I did this, and i got the error
"Invalid WNS credentials"
The secret was sourced from Entra ID -> Application -> certifications & Secrets -> New Secret
I tried both the secret values and got the same error both times

The SID i took from "product information" under the overview for the application registered in Microsoft Dev center. It was copy pasted to ensure that it was correct.

Azure trouble shooting indicates that the secret key should be provided upon registering the applcation in microsoft dev center. Is this false?
Bror Vedeld 0 Reputation points

2025-02-13T11:22:40.97+00:00

The Azure application and the Microsoft developer center application were created independently (With the same account), Is this relevant?
Bror Vedeld 0 Reputation points

2025-02-13T11:29:49.1566667+00:00

@Bhargavi Naragani

I did this, and i got the error "Invalid WNS credentials" The secret was sourced from Entra ID -> Application -> certifications & Secrets -> New Secret I tried both the secret values and got the same error both times

The SID i took from "product information" under the overview for the application registered in Microsoft Dev center. It was copy pasted to ensure that it was correct.

Azure trouble shooting indicates that the secret key should be provided upon registering the application in microsoft dev center. Is this false?

The Azure application and the Microsoft developer center application were created independently (With the same account), Is this relevant?
"you should make sure that you have both the Package Security Identifier (SID) and the secret key of the Microsoft Developer application."

How do i get the secret key from the Microsoft Developer Application?
Bhargavi Naragani 7,940 Reputation points Microsoft External Staff Moderator

2025-02-13T12:28:50.68+00:00
Hi @Bror Vedeld,

The Microsoft Entra ID (previously Azure AD) is not the secret key needed for WNS. Rather, it must be generated from the Microsoft Partner Center (Dev Center) where your application is registered, Entra ID secret key is used for OAuth authentication for APIs but not the right key for WNS authentication. WNS needs the secret key associated with the registration in Dev Center, not Azure AD.

Upon registering an app in Microsoft Partner Center, you obtain:
Package Security Identifier (SID) is located under Product Identity
No Secret Key is automatically supplied. It needs to be manually created under the App Management section.

To get or create the secret key, follow these steps:
Log in to Microsoft Partner Center.
Go to Account settings → App Management → App Identity.
Find the Application Secrets section.
If there is no secret key, click Add a new secret key: Name it. Set an expiration time, click Create, then copy the key right away (it won't be displayed again).

Since your Azure app and Microsoft Developer Center app are independently created, you must ensure that your Azure app registration is properly set to match your registered app's identity within the Developer Center.
Open the Azure Portal (https://portal.azure.com)
Go to Azure Active Directory → App registrations, locate your Azure app and open it.
Under Certificates & secrets, insert the WNS secret key retrieved from the Microsoft Developer Center Under API Permissions, make sure Access Windows Push Notification Services (WNS) is checked.

However, as long as you have the right SID and the secret key from Microsoft Partner Center, they should be compatible.
To authenticate with WNS, use:
Your SID from Dev Center and the secret key from Partner Center.

Reference:
https://learn.microsoft.com/en-us/windows/apps/design/shell/tiles-and-notifications/windows-push-notification-services--wns--overview
https://learn.microsoft.com/en-us/partner-center/enroll/overview
https://learn.microsoft.com/en-us/windows/apps/design/shell/tiles-and-notifications/push-request-response-headers

If you have any further concerns or queries, please feel free to reach out to us.
If the answer is helpful, kindly Upvote it.
Bror Vedeld 0 Reputation points

2025-02-13T14:18:29.28+00:00

Hi @Bhargavi Naragani

I cannot see the App management option under Account settings, are you sure this is correct?
Do i need to submit my application with all the payment options and the like to microsoft store in order to get it through?
Bhargavi Naragani 7,940 Reputation points Microsoft External Staff Moderator

2025-02-13T17:32:08.0133333+00:00

Hello @Bror Vedeld,
App Management section may not always be readily apparent, depending on your permissions and account settings.
Search for Application Secrets or App Management within the identity section.

Regarding your application submitting with all payment options, you don't have to publish your app or enable payments in order to acquire WNS credentials. But your app should be correctly registered within Partner Center under a valid identity and package information.

https://learn.microsoft.com/en-us/answers/questions/2156980/invalid-wns-credentials-error-when-setting-up-new

if you have any further query do let us know.
Bhargavi Naragani 7,940 Reputation points Microsoft External Staff Moderator

2025-02-14T18:29:18.63+00:00

Hi @Bror Vedeld,
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.
Bhargavi Naragani 7,940 Reputation points Microsoft External Staff Moderator

2025-02-17T05:04:11.2066667+00:00

Hi @Bror Vedeld,
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.
Microlead Software 86 Reputation points

2025-05-18T04:09:05.0666667+00:00

I have the same issue, the problem is the needs to map the PFN to its Azure AppID for the WNS to work and the hub authenticate.What do we need -as Microsoft- is:

If your app is a packaged Win32 app, then create a Package Family Name (PFN) mapping request by emailing Win_App_xxx_xxxx@microsoft.com with subject line "Windows App SDK Push Notifications Mapping Request" and body "PFN: [your PFN]", AppId: [your APPId], ObjectId: [your ObjectId]. Mapping requests are completed on a weekly basis. You will be notified once your mapping request has been completed.

but the email to Win_App_xxx_xxxx@microsoft.com always return undelivered. and without mapping the WNS will not work.
Microlead Software 86 Reputation points

2025-05-18T13:29:15.02+00:00

I have the same issue, the problem is the needs to map the PFN to its Azure AppID for the WNS to work and the hub authenticate.What do we need -as Microsoft- is:

If your app is a packaged Win32 app, then create a Package Family Name (PFN) mapping request by emailing Win_App_xxx_xxxx@microsoft.com with subject line "Windows App SDK Push Notifications Mapping Request" and body "PFN: [your PFN]", AppId: [your APPId], ObjectId: [your ObjectId]. Mapping requests are completed on a weekly basis. You will be notified once your mapping request has been completed.

but the email to Win_App_xxx_xxxx@microsoft.com always return undelivered. and without mapping the WNS will not work.