Update Adventure Works RI Networking Information

[jtracey93]

This PR fixes

• The 2nd part of issue Provide networking details for hub and spoke #573

[victorar]

Thanks for the contribution Jack. There is no need to explain how hub and spoke works as that's already documented in multiple other Microsoft articles.

Instead of that, please just add a small diagram for a hub and spoke architecture, such as figure 2 on this article: https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/ready/azure-best-practices/traditional-azure-networking-topology

And mention that spokes use shared resources in the hub such as ExpressRoute and/or VPN GW, and that transit routing across spokes is achieved by VNet peering, UDR and transit via NVA.

[jtracey93]

Thanks @victorar. Have removed the traffic flow section and included links to all the relevant docs.

Have left the new additional diagram as I think this really helps explain and portray how the networking architecture fits with the Management Groups & Subscription organisation in the wider context of Enterprise Scale 👍

[victorar]

Thanks for your contributions, Jack.

There is no need for a dedicated section for hub and spoke network topology in this article. Instead, within the introduction or customer profile section, just provide a short blurb of what a hub and spoke network topology is, and provide a simple/generic diagram of a hub and spoke network such as the one I shared previously. Then, you can add a link for further details, as well as design considerations and recommendations for hub and spoke networks in ESLZ: https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/ready/azure-best-practices/traditional-azure-networking-topology

[jtracey93]

Hey Victor, no problem.

Have made further updates.

[victorar]

I made some updates in your fork/branch. Let me know what you think :)

[jtracey93]

All good with me 👍