Giter Site home page Giter Site logo

microsoft / industry Goto Github PK

View Code? Open in Web Editor NEW
244.0 35.0 71.0 108.32 MB

This repository provides holistic architecture design and reference implementation for industry cloud based on proven success of large scale deployments and at-scale adoption with customers and partners.

License: MIT License

PowerShell 28.40% Bicep 71.60%

industry's Introduction

Introduction

This repository provides holistic architecture design and reference implementation for industry cloud based on proven success of large scale deployments and at-scale adoption with customers and partners. This guidance is built by active inner-source community inside Microsoft to help customers and partners by providing prescriptive and actionable guidance and implementation to accelerate deployment and adoption of industry cloud.

Microsoft Cloud for industries will take a dependency on well-architected, sustainable, and scalable cloud foundations (Microsoft Azure, Microsoft Power Platform, and Microsoft 365), which will de-risk technical debt and ensure durable solutions regardless of the industry cloud reference architecture your organization would need. This repository references and provides proven, authoritative, and prescriptive architecture and design recommendations for these foundations, as well as specific reference implementations targeting the unique industry requirements. See the following article to learn more

Industry Cloud Reference Architectures

Healthcare

Microsoft Cloud for Healthcare spans the Microsoft Clouds (Azure, Power Platform and Microsoft 365). This repository provides prescriptive architecture and design guidance together with respective reference implementations for the industry solution as a whole, as well as the various healthcare capabilities.

Healthcare Scenario Reference Architecture

Healthcare Foundations (Recommended)

Healthcare Solutions

Telecommunications

Microsoft Cloud for Telecommunications enables an at-scale, and sustainable architecture for telecommunications specific workloads, catering for the unique set of requirements the telecommunications industry has compared to enterprises or customers in other industries. A prescriptive architecture and design guidance is summarized below.

Telecommunications Scenario Reference Architecture

Telecommunications Foundations (Recommended)

Telco Solutions

Retail

Microsoft Cloud for Retail is an industry-specific cloud composed of products and services to address retail specific use-cases. With services across Microsoft Azure, Dynamics 365 and Power Platform, customers can design, build and deploy cross-cloud solutions.

Retail Services Reference Architecture

Financial services

Microsoft Cloud for Financial Services provides capabilities to manage data to deliver differentiated experiences, empower employees, and combat financial crime while facilitating security, compliance, and interoperability.

Financial Services Reference Architecture

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

Trademarks

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.

Microsoft Sponsorship

The Industry Reference Architecture project was created by the Microsoft Customer Architecture Team (CAT) in partnership with several Microsoft engineering teams who continue to actively sponsor the sustained evolution of the project through the creation of additional reference implementations for common industry scenarios.

industry's People

Contributors

amanjeetsingh avatar andrehass avatar anttipajunen avatar arielsepulveda avatar caeswor avatar cgill avatar daltondhcp avatar esbran avatar hjscherer avatar krnese avatar luisefreese avatar mahesh-msft avatar marvinbuss avatar microsoftopensource avatar mswantek68 avatar rcarmo avatar rocavalc avatar sasever avatar sofijamj avatar uday31in avatar victorar avatar yannickre avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

industry's Issues

AfO: Complete documentation

Describe the solution you'd like

  • Ensure all links are working to navigate
  • Expand on "Distributed Edge"
  • Expand on Lighthouse & Managed App
  • Add "Operator" article focusing on AzMon, LA, NSG Flow Logs, Traffic Analyzer and PowerBi

AfO: Readiness and training

Describe the solution you'd like

  • Develop content for readiness and training, using content and artifacts from Industry repository
  • Define timelines for execution

Bug Report: IoT Connector Name Not being Validated.

When a user deploys the solution and specifies an invalid IoT connector name, the template does not validate that input before attempting to deploy to Azure, which causes the deployment to fail: with the following error:

{
"status": "Failed",
"error": {
"code": "BadRequest",
"message": "Name can contain only lowercase letters, numbers and the '-' character."
}
}

AfO: Power Point L100, L200

Describe the solution you'd like

  • Power Point presentation for "AfO Architecture" as foundation for telco workloads

Feature Request

Describe the solution you'd like

  • IoMT
  • Care Management
  • Home Health (#64)
  • fix link (#62)
  • Clinical and operations insights --> indenting other ones (#62)

Feature Request: Add Projects to Repository

Describe the solution you'd like
I would propose to add a Project per industry cloud/ cross-cloud solution. Let's discuss internally how we would like to track progress and commitment to specific tasks.

Also, I would propose to keep everything in GitHub to keep things simple and not move between different environments.

Update Telco diagram

Describe the solution you'd like

  • Update diagram - close on naming vs leave it to customer to specify during deployment

Complete Patient Service Center scenario

Describe the solution you'd like

  • Outline the critical design areas
  • Document required sequence for complete setup
  • Environments, Customer Insights, add-ons, Omnichannel etc.
  • Solution Center

Update Telco RI

Describe the solution you'd like

  • Update and align with diagram and recommendations
  • Either use decided name for management group or ask for customer input during deployment

Bug Report: typo in Telco readme heading

Describe the bug
Typo in the Telco readme.md title. It should be be 'Telecommunications' (double m) but currently is spelled 'Telecomunnications' (double n).

Note: once the typo is fixed, it will change the URL of the readme.md.

Steps to reproduce

  1. visit readme.md and review the first line.

Screenshots

Feature Request - SCTP Flow support

Describe the solution you'd like

Again, when and where appropriate, including gatewayLB and its SCTP support I think will be common across all telcos.

Telco RI deployment options and sequence

Describe the solution you'd like
The deployment experience, options and sequence should address the following:

  • Foundation is industry agnostic for all Microsoft clouds, and will leverage existing artifacts as is (e.g., ESLZ reference implementation)

  • Industry specific scenarios (separate) taking a dependency on Foundation being deployed first

  • Foundation + Industry specific scenarios (all together) will 1) point to existing artifacts as is, and then sequence the remaining deployments from the industry repository

  • With the above in place, additional Telco industry specific scenarios can be added (i.e., scale-out networking for vhub, and vwan)

DR for FHIR

What is the recommended DR solution for FHIR. How to enable and configure it.

Bug Report: update obsolete name in Telco diagram

Describe the bug
The architecture illustration in the Telco repo currently has elements labeled 'Security Center'. At Ignite 2021 the 'Security Center' name was retired, replaced with 'Microsoft Defender for Cloud', a renaming that now also covers what used to be Azure Defender.

For more, refer to this official Microsoft blog.

Suggested to update the diagram accordingly, and ensure the icon is accurate.

Steps to reproduce

  1. View the Telco Architecture diagram to see what is mentioned.

Screenshots

North Star for PP: Reference implementation

Describe the solution you'd like

  • Reference implementation where Azure is the anchor (Ux + ARM)

  • Reference implementation without Azure (PowerShell)

  • [Optional] solution from within Power Platform

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.