The same table, notification center and server for two applications

Question

We ended up at Microsoft, abandoning Silverlight and focusing on UWP. This ended up having to develop two applications with two applications (UWP and Silverlight) that left us with two applications that cannot be combined / packaged together. Therefore, we decided to use the application as a companion application.

Both applications use authentication, currently related to Microsoft authentication. The services used for authentication are of the type Azure App Service - Mobile . In addition to authentication, services also provide interfaces to the notification hub, block storage, and SQL storage.

Therefore, the question arises: is it possible to have one App Service - Mobile (rather than mobileservice) and authenticate two different applications using the same service? In addition, can the same Notification Hub be used to send notifications for different applications?

Or, we need to create two different services for each application to facilitate the use of authentication and push messages. Then we can link the same database with two App Service - Mobile ? But this leaves the question of notification nodes that do not have the same registrations?

Answer 1

According to the product group, the idea of ​​the Mobile App is to be a separate backend. To do this, the Mobile Apps control panel should have not one field for PackageId / ..., but two or more for the backend for different applications. Each connection between an application and an external service, such as an authentication provider or push notification platform, is "personalized" - by identifiers and password or certificates, or for many reasons.

I can imagine a scenario where someone would need to connect one server to different applications, but the idea of ​​Azure Mobile App is different. And, since the App Service is a service, I think that in the current situation, what you want to do is impossible.

Answer 2

I do not think that you can have several applications connected to one Azure mobile application. You can connect the same application on different platforms, but not to several applications for the same platform as a mobile application designed for an individual application. Check out this feedback request. https://feedback.azure.com/forums/218849-notification-hubs/suggestions/3821272-push-notifications-for-multiple-apps

Answer 3

Azure Mobile app consists of a client application and backend in Azure. There does not stop reusing the same backend for multiple applications.

Answer 4

We currently have more than 30 applications on 2 platforms, and all of them use the same Azure mobile application. However, we cannot use push notifications in different applications yet .... It seems that the Azure mobile application allows only one hub, and the hub allows only one application identifier to be registered .... It seems that the mobile application services therefore have more functionality than the push service. If this estimate is correct, it may seem an oversight to allow the engine to deliver more power than the axis can withstand ... it is logical that they should be aligned ... since there are expectations and assumptions derived from an earlier engine performance test from the same manufacturer as the bridge ....