microsoft / industry Goto Github PK

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.

• fix link (#62)
• Clinical and operations insights --> indenting other ones (#62)

Describe the bug
Supported Regions need to be updated. Following regions are supported based on my research:

Describe the solution you'd like
Add the health assistant scenario guidance for MC4H.

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

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.

Describe the solution you'd like

• Update documentation before going live
• Complete diagrams
• Add Dataverse for Teams to the design area (Environemnt, governance)

Describe the solution you'd like

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

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

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

Describe the bug

Swap the order of converter and proxy.
Events are only created from the FHIR service (currently)

Screenshots

Include NSG Flow Log visualization via Power BI in Telco architectural diagram

Describe the bug
@esbran Please take a look here: https://github.com/microsoft/industry/tree/main/healthcare#post-deployment

Describe the solution you'd like

The existing architecture diagram for Azure for Telecommunications does not depict the telco's nor the customer's AAD tenant.

Describe the solution you'd like

• Add context and content for considerations and recommendations for Telco design areas

Describe the solution you'd like

• Complete e2e "AfO Architecture" experience
• Include "Operator dashboard"

Describe the solution you'd like

Deploy Healthcare Analytics solution
ARM + Portal

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."
}
}

Describe the solution you'd like

• Describe industry context for Power Platform
• Call out industry specific requirements per design areas as appropriate

Describe the solution you'd like

• Deployment experience and template for LZ scale-out experience for Telco scenarios

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)

Describe the solution you'd like

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

Describe the solution you'd like

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

Describe the bug

Screenshots
Please upload PowerApp Visio.

Describe the solution you'd like
In the connectivity tab, we must provide option to create and configure the subnet dedicated for Microsoft.PowerPlatform/vnetaccesslinks, to prepare for Dataflows from Power Platform environment(s)

Network Cloud is not yet in any level of official preview, but if this is getting presented internally, I definitely think we should include it in some way as It'll be a massive component once GA.

Describe the solution you'd like
Add the patient outreach scenario guidance for MC4H.

Describe the solution you'd like
Add Solution pattern for Data-driven Application using Power Platform.

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

Describe the bug
Same issue as described here: https://github.com/github/super-linter/issues/1897

Steps to reproduce

1. Create Fork
2. Submit PR back to main

Screenshots
See here: https://github.com/github/super-linter/issues/1897

Describe the solution you'd like

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

Describe the bug

• Storage account name is generated based on the workspace name, and is not capped at 24 characters
• Remove usage of hyphens in storage account name

Describe the solution you'd like
Add the care management scenario guidance for MC4H.

Describe the solution you'd like

• Describe the North Star architecture framework to contextualise the Power Platform part
• Definition done & success

Describe the solution you'd like
Add the Clinical Analytics scenario guidance for MC4H.

Provide prescriptive guidance with design considerations and recommendations for the Azure for Telco Industry Reference Architecture.

Describe the solution you'd like

• Finalize Power Point presentation for North Star for Power Platform
• Review

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

Describe the solution you'd like
Add the home health scenario guidance for MC4H.

Describe the bug
The codeowner file references the wrong team and also does not specify rules in the correct order. Lastly, the paths require some updates.

Describe the solution you'd like

• Develop training content
• Plan for timelines and execution

Provide a high-level (100-level) architectural diagram for the Azure reference architecture for Telco industry.

CC: @selims88

Describe the solution you'd like

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

Describe the solution you'd like
Add a doc that describes the requirements and setup of Azure Synapse Link for Dataverse.

Provide prescriptive guidance with design considerations and recommendations for the Azure for Telco Industry reference architecture.

Describe the solution you'd like
Add the Virtual Visits scenario guidance for MC4H.

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

Describe the solution you'd like
Integrate doc quality checks.