@Casper Rubæk Thanks for reaching out.
Service Bus is a fully managed enterprise message broker with message queues and publish-subscribe topics. The service is intended for enterprise applications that require transactions, ordering, duplicate detection, and instantaneous consistency. I will not suggest you to leverage the service bus for push notification to mobile devices as there would be multiple issues as you need to manage the device registration (adding, deleting, tag feature etc.) along with the mapping of individual devices to the individual subscription at your end. Your individual devices will be connecting to the single subscription for getting the message content of your notification. There is a limitation of 2K subscription per topic so you can only have 2K subscription, but you can auto forward feature. As the service bus is the pull model your devices should always be checking if there is any message that is available to be consumed. It will be more like building your own solution for handling all the features that notification hub already provides for you.
Notification Hub already provides an easy-to-use and scaled-out push engine that enables you to send notifications to any platform (iOS, Android, Windows, etc.) from any back-end (cloud or on-premises). Notification Hubs works great for both enterprise and consumer scenarios. Notification hub passes the notification to the PNS handle and PNS handle is the one who is responsible to deliver the messages to your devices.
Let me know if you have any queries or concerns.
Please 'Accept as answer' and ‘Upvote’ if it helped so that it can help others in the community looking for help on similar topics.