There is a command group 'az_network_cross connection_peering'. This group of commands could 'manage expressroute peering of an expressroute cross connection'. The group of commands has global parameter '--debug' which means 'Increase logging verbosity to show all debug logs.'. The group of commands has global parameter '--help -h' which means 'Show this help message and exit.'. The group of commands has global parameter '--only-show-errors' which means 'Only show errors, suppressing warnings.'. The group of commands has global parameter '--output -o' which means 'Output format.'. The group of commands has global parameter '--query' which means 'JMESPath query string. See <a href="http://jmespath.org/">http://jmespath.org/</a> for more information and examples.'. The group of commands has global parameter '--subscription' which means 'Name or ID of subscription. You can configure the default subscription using `az account set -s NAME_OR_ID`.'. The group of commands has global parameter '--verbose' which means 'Increase logging verbosity. Use --debug for full debug logs.'. This group contains a child command 'az_network_cross connection_peering_create'.The syntax is: az network cross-connection peering create --cross-connection-name
                                           --peer-asn
                                           --peering-type {azureprivatepeering, azurepublicpeering, microsoftpeering}
                                           --primary-peer-subnet
                                           --resource-group
                                           --secondary-peer-subnet
                                           --vlan-id
                                           [--advertised-public-prefixes]
                                           [--customer-asn]
                                           [--routing-registry-name {afrinic, altdb, apnic, arin, lacnic, level3, radb, ripencc}]
                                           [--shared-key]. The 1th example of the child command would be to use it to 'create microsoft peering settings with ipv4 configuration', the syntax is: az network cross-connection peering create -g MyResourceGroup --cross-connection-name MyCircuit \
    --peering-type MicrosoftPeering --peer-asn 10002 --vlan-id 103 \
    --primary-peer-subnet 101.0.0.0/30 --secondary-peer-subnet 102.0.0.0/30 \
    --advertised-public-prefixes 101.0.0.0/30. The parameter '--cross-connection-name' is required. It is used to expressroute cross-connection name.. The parameter '--peer-asn' is required. It is used to autonomous system number of the customer/connectivity provider.. The parameter '--peering-type' is required. It is used to bgp peering type for the circuit.. The parameter '--primary-peer-subnet' is required. It is used to /30 subnet used to configure ip addresses for primary interface.. The parameter '--resource-group -g' is required. It is used to name of resource group. you can configure the default group using `az configure --defaults group=<name>`.. The parameter '--secondary-peer-subnet' is required. It is used to /30 subnet used to configure ip addresses for secondary interface.. The parameter '--vlan-id' is required. It is used to identifier used to identify the customer.. The parameter '--advertised-public-prefixes' is optional. space-separated list of prefixes to be advertised through the bgp peering.. The parameter '--customer-asn' is optional. autonomous system number of the customer.. The parameter '--routing-registry-name' is optional. internet routing registry / regional internet registry.. The parameter '--shared-key' is optional. key for generating an md5 for the bgp session.. 