No response to Windows App SDK push PFN mapping request after 7 days, push still 403

A packaged Windows App SDK app cannot send push notifications until Microsoft completes its PFN-to-Azure AppId mapping; after one full weekly processing cycle without confirmation, preserve the WNS diagnostics and escalate through the public WindowsAppSDK issue tracker rather than resending the same request.

First, clarify the request date

The stated date, October 22, 2027, is in the future relative to the current date. If that is a typo, use the actual sent date when calculating the delay and when escalating. Include the original email’s timestamp and delivery status, but do not post the PFN, tenant ID, application ID, object ID, client secret, or complete channel URI publicly.

What the seven-day delay means

For an MSIX-packaged app or an app packaged with external location, the PFN mapping is mandatory. Microsoft documents that requests are processed weekly and that notification is sent after completion.^1^

Seven elapsed days do not necessarily mean that the request has passed through a weekly batch—for example, it may have arrived just after one. However, push sending will not work while the mapping remains incomplete.

Recent public WindowsAppSDK reports also describe mapping-mailbox failures and subsequent WNS 403 responses, including a case where the documented mailbox rejected the message.^2^ A second issue reports the same inability to submit the mapping request.[^3^](https://github.com/microsoft/WindowsAppSDK/issues/6698 "Cannot send "Windows App SDK Push Notifications Mapping Request" mail ...")

Escalate after the weekly cycle

If there is still no completion notice after the next weekly processing opportunity:

1. Check the original message’s delivery status for a nondelivery report or rejection. Do not resend it unless Microsoft asks for that.
2. Open or add details to a public microsoft/WindowsAppSDK GitHub issue with the area-Notifications label.
3. Include:
   • Actual request date and time, including time zone.
   • Confirmation that this is a packaged Windows App SDK application.
   • Windows App SDK version.
   • Whether Register() and CreateChannelAsync() succeed.
   • WNS response status and response headers.
   • Whether the mapping email was accepted or bounced.
4. Redact all credentials and identifiers. In particular, never include the client secret, Bearer [Token], or complete channel URI.

Capture the WNS evidence

A WNS 403 Forbidden means the request was authenticated, but the access token does not match the credentials associated with the app that obtained the channel URI.^4^ An incomplete PFN mapping is consistent with this situation, but 403 alone does not prove that mapping is the only problem.

Log these response headers for escalation:

• HTTP response code
• X-WNS-Debug-Trace
• X-WNS-Msg-ID
• MS-CV

Microsoft identifies the correlation vector, debug trace, and message ID as required when reporting a WNS problem.^5^

If Microsoft confirms that mapping is complete

Only then pivot to configuration troubleshooting:

1. Confirm the Entra app registration is multitenant.
2. Confirm the submitted Object ID is the service principal’s Object ID reached through Managed application in local directory, not the Object ID shown on the app registration’s Essentials page.
3. Confirm the Azure AppId used to request the channel is the same AppId represented by the access token used for the WNS send.
4. For packaged apps, confirm <com:Class Id="..."> in Package.appxmanifest contains that same Azure AppId.
5. Generate a fresh channel URI after correcting any identity mismatch, then obtain a fresh access token and retry.

These identity and manifest requirements are part of the Windows App SDK push setup.^1^

References

1. Quickstart: Push notifications in the Windows App SDK
2. Windows App SDK Push: documented PFN mapping mailbox bounces ... - GitHub
3. Cannot send "Windows App SDK Push Notifications Mapping Request" mail ...
4. Troubleshooting push notifications
5. Push notification service request and response headers (Windows Runtime apps)