Notification Hub - Can't add WNS service - Invalid WNS credentials

Hi comor,
Apology for your Inconveniences. We noticed your recent experience on the Q&A community platform was rated low (Answer provided was not helpful). Thank you for taking time to share your feedback.

Here few suggestions for your query may help you:

While the package SID is obtained correctly from the partner center under the App Identification, the Azure notification hub has not been shown in the Hub, the customer in the secret / safety key partner center required to configure the WNS (Windows notification service). It is expected - the safety key must be generated separately.
You can go to Azure portal: Azure Active Directory > App registrations, register your app
https://apps.dev.microsoft.com/

Match it with the identity of your app (using the same package SID) in the partner center.

Under "Certificate and Raj", click on "New Customer Secret".

This mystery will serve as WNS safety key.

Under authentication, verify that the platform includes "mobile or desktop applications" and valid redirected URIs.
After this process you can paste Package SID (from Partner Center). and Paste the Client Secret (from the App Registration portal). in Notification Hub and then click on save.

Hi comor, 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.

Hi comor, 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.

I'm not sure if you are a maintenance staff of Azure, or if you have recently operated or tested this kind of application. If possible, please try to operate it by yourself first and make sure it succeeds before answering this question. Otherwise, it may waste each other's time.

Hi comor, Sorry for the inconvenience. We are experiencing access-related issues on our end. We will get back to you on this.

Thank you for your patient reply. I believe that many developers who develop such WNS Apps will encounter this kind of problem. If there is any latest progress, please reply here or send a message or an email. I would be extremely grateful.

Hi comor,sure

I have the same issue (Invalid WNS credentials.), i followed Microsoft documentation till Step 4 which is mapping the App PFN to its Azure AppId by sending a map request to
i think #comor has the same situation, need to map the App PFN to its Azure AppId for the credentials to be valid.

i don't know why Microsoft still use manual mapping not automatic mapping like adding a section to the Azure registered app to map the Partner Center App PFN to its Azure AppId?

Hello @Microlead Software ,Sorry for the inconvenience. We are experiencing access-related issues on our end. We will get back to you on this.

Thanks for the update @Sampath . I'll wait for your follow-up, as the PFN-to-Azure AppId mapping is a blocking issue for enabling WNS in production. Please let us know once the email channel is working or if there’s an alternative procedure we can use in the meantime.

If there's any workaround or manual intervention possible in the interim, I’d be very grateful, we’re currently unable to proceed with push notifications due to the WNS authentication failure.

Hi @Sampath ,
For reference, here’s the full error returned when trying to email Win_App_SDK_Push@microsoft.com:

CY4PEPF0000E9D6.mail.protection.outlook.com rejected your message to the following email addresses:

Win_App_SDK_Push@microsoft.com (Win_App_SDK_Push@microsoft.com)

Your message was rejected by the recipient's domain because the recipient's email address isn't listed in the domain's directory. It might be misspelled or it might not exist. Try to fix the problem by doing one or more of the following:

Send the message again - delete and retype the address before resending. If your email program automatically suggests an address to use, don't select it - type the complete email address.

Clear the recipient Auto-Complete List in your email program by following the steps in this article. Then resend the message.

For Email Administrators

Directory based edge blocking is enabled for the recipient's organization and the recipient wasn't found in their directory. If the sender is using the correct address but continues to experience the problem, contact the recipient's email admin and tell them about the problem. To fix this they should resynchronize their on-premises and cloud directories.

CY4PEPF0000E9D6.mail.protection.outlook.com gave this error:

Recipient address rejected: Access denied. For more information see https://aka.ms/EXOSmtpErrors [CY4PEPF0000E9D6.namprd05.prod.outlook.com 2025-05-18T03:56:02.207Z 08DD948BBACB413A]

Hi, we are facing the same issues, getting invalid wns credentials even though the Package SID and Security Key is correct.
Is there any update on this issue?