Added networking components to Azure naming conventions

[tomling]

As part of this change (In collaboration with Andrew Poole) we have come up with finer grain naming conventions for networking components in Azure .

[tomling]

This is my first Github pull request (sorry if I've done it incorrectly) 😁

[MarcDenman]

Thank you :) Can you double check the examples provided to the patterns please? A few don't have start with the Cloud Key though specified in the pattern, a few might be missing hyphens or the pattern have hyphens not needed, I don't know which!

[tomling]

Thank you :) Can you double check the examples provided to the patterns please? A few don't have start with the Cloud Key though specified in the pattern, a few might be missing hyphens or the pattern have hyphens not needed, I don't know which!

Thanks Marc I will add the cloud key to the examples. @thealmguy can you confirm if the hyphens are compulsory?

[elduddz]

Thank you :) Can you double check the examples provided to the patterns please? A few don't have start with the Cloud Key though specified in the pattern, a few might be missing hyphens or the pattern have hyphens not needed, I don't know which!

Thanks Marc I will add the cloud key to the examples. @thealmguy can you confirm if the hyphens are compulsory?

hyphens are not compulsory if they will take you over the resource name limit

When using resources with short character limits, omit hypens as a first step

[elduddz]

this branch needs to be committed before we close the naming conventions