Solution ideas

This article describes a solution idea. Your cloud architect can use this guidance to help visualize the major components for a typical implementation of this architecture. Use this article as a starting point to design a well-architected solution that aligns with your workload's specific requirements.

This solution idea helps to improve employee productivity and speed decision making by giving legacy processing applications a modern day front end. This line-of-business application solution consolidates data from multiple business systems. It then presents the data in web and mobile front ends.

Potential use cases

Organizations that want to connect disparate legacy systems and give users access through a mobile UI can benefit from this solution. Legacy systems include:

  • Sales order entry and inventory systems.
  • Hospital databases.
  • Insurance billing and claims software.
  • Banking systems.

Architecture


 Download an SVG of this architecture.

Dataflow

  1. Customer's mobile app authenticates via Azure Active Directory B2C.
  2. Customer's mobile app connects to the back-end web service that aggregates data from different systems using asynchronous connection.
  3. Web application connects to SQL database.
  4. Power BI connects to SQL database and SharePoint.
  5. Logic app pulls data from CRM (Salesforce).
  6. Logic app connects to SAP system (on-premises or in the cloud).
  7. Employee mobile app connects to the logic app that orchestrates the business process.
  8. Employee mobile app authenticates via Microsoft Entra ID.

Components

  • Azure Virtual Machines lets you deploy a Windows Server or Linux image in the cloud. You can select images from a marketplace or use your own customized images.
  • Azure SQL Database is a relational database service that lets you rapidly create, extend, and scale relational applications into the cloud.

Next steps