Unauthorized, invalid SAS token accessing Notification Hub rich telemetry using Standard Tier

Question

Unauthorized, invalid SAS token accessing Notification Hub rich telemetry using Standard Tier

Christopher Meehan 0

I have tried every permutation I can find and or co-author with GitHub CoPilot Pro. I recently changed from the Free Tier to the Standard Tier so I can access per message telemetry in an attempt to verify a payload being sent using device registered templates. I want to see the body and data being sent after receiving a payload from an Azure Function.

I have a little console program in C# that can view device registrations, tags, templates but now matter what I do to construct a SAS token and REST API query, via my c# console app or Postman, I get an invalid SAS token.

I found a post, which I can't find now of course that someone engaged support and after switching from Free to Standard, support had to clear some cache on the backend and it started working.

Pulling my hair out. Any help? Happy to share any content that will help.

-Chris

Prabhavathi Manchala 1,050 Reputation points Microsoft External Staff

2025-04-16T00:15:55.3033333+00:00
Hi Christopher Meehan,

You're seeing a 401 error with an invalid SAS token when accessing telemetry after switching to the Standard Tier. Other features still work, but telemetry needs extra permissions your token might be missing. After upgrading to the Standard tier, features like telemetry might not work right away due to backend caching, even if your SAS token is correct.

Make sure you're creating the SAS token correctly in your C# app and Postman. Also, ensure the token is added to the request headers like this.

Authorization: SharedAccessSignature sr={resourceUri}&sig={signature}&se={expiry}&skn={keyName}

Tier upgrades can sometimes cause backend cache issues, preventing the system from recognizing valid SAS tokens until the cache is cleared.

Ensure the SAS token has the correct permissions for the Standard Tier, including access to telemetry data.

When upgrading tiers, you may need to regenerate existing SAS tokens to align with the new authentication requirements.

In the Azure portal → Go to your Notification Hub → Under Settings select Access Policies → Regenerate primary and secondary keys → Create new SAS tokens with the updated keys.

Make sure your request includes the correct API version (2017-04-01 or later) to access features like per-message telemetry in the Standard Tier.

GET https://{namespace}.servicebus.windows.net/{NotificationHub}/telemetry?api-version=2017-04-01

https://learn.microsoft.com/en-us/rest/api/notificationhubs/get-notification-message-telemetry
Prabhavathi Manchala 1,050 Reputation points Microsoft External Staff

2025-04-16T20:21:10.6266667+00:00

Hi Christopher Meehan,

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.
Laxman Reddy Revuri 4,000 Reputation points Microsoft External Staff

2025-04-17T23:18:45.4+00:00

Hi Christopher Meehan,

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.

Your answer

Prabhavathi Manchala 1,050 Reputation points Microsoft External Staff

2025-04-16T00:15:55.3033333+00:00

Hi Christopher Meehan,

You're seeing a 401 error with an invalid SAS token when accessing telemetry after switching to the Standard Tier. Other features still work, but telemetry needs extra permissions your token might be missing. After upgrading to the Standard tier, features like telemetry might not work right away due to backend caching, even if your SAS token is correct.

Make sure you're creating the SAS token correctly in your C# app and Postman. Also, ensure the token is added to the request headers like this.

Authorization: SharedAccessSignature sr={resourceUri}&sig={signature}&se={expiry}&skn={keyName}

Tier upgrades can sometimes cause backend cache issues, preventing the system from recognizing valid SAS tokens until the cache is cleared.

Ensure the SAS token has the correct permissions for the Standard Tier, including access to telemetry data.

When upgrading tiers, you may need to regenerate existing SAS tokens to align with the new authentication requirements.

In the Azure portal → Go to your Notification Hub → Under Settings select Access Policies → Regenerate primary and secondary keys → Create new SAS tokens with the updated keys.

Make sure your request includes the correct API version (2017-04-01 or later) to access features like per-message telemetry in the Standard Tier.

GET https://{namespace}.servicebus.windows.net/{NotificationHub}/telemetry?api-version=2017-04-01

https://learn.microsoft.com/en-us/rest/api/notificationhubs/get-notification-message-telemetry
Prabhavathi Manchala 1,050 Reputation points Microsoft External Staff

2025-04-16T20:21:10.6266667+00:00

Hi Christopher Meehan,

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.
Laxman Reddy Revuri 4,000 Reputation points Microsoft External Staff

2025-04-17T23:18:45.4+00:00

Hi Christopher Meehan,

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.

Share via

Unauthorized, invalid SAS token accessing Notification Hub rich telemetry using Standard Tier

Your answer