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