Azure Notification Hubs: One Push, a Million Phones

Frequently asked questions

Why not just loop over device tokens and call each push service yourself?

A million individual calls to APNs, FCM and WNS takes too long to still be relevant by the time it finishes, and it means your code has to know the payload format each platform expects. Notification Hubs takes one send and fans it out as the correct payload per platform.

How do you target an audience without storing device tokens yourself?

Tag targeting — you describe the audience (for example, premium users in a region) and Notification Hubs resolves which registered devices match, so your application code never has to hold or manage device tokens directly.

Read deeper on Azure

Twenty seconds gets the shape of an idea across. These go into how it behaves in production.

• AI Bot Attacks on a Mobile App Login, and How Azure Stops Them

  A script tries 8,000 passwords a minute against your login API at 3am. Rate limiting, smart lockout and Defender for Cloud make speed the losing move.

• Azure Key Vault Explained: The One Secret Tutorials Never Remove

  Moving every secret into Key Vault leaves exactly one behind: the credential that opens the vault. A managed identity is what removes it.

• How to Secure a Mobile API on Azure in Five Steps, in the Right Order

  HTTPS only, authentication, authorization, secrets and monitoring: five steps to secure a mobile API on Azure, and why the order carries most of the value.