There is a command group 'az_eventgrid_domain'. This group of commands could 'manage event domains'. 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_eventgrid_domain_create'.The syntax is: az eventgrid domain create --location
                           --name
                           --resource-group
                           [--identity {noidentity, systemassigned}]
                           [--inbound-ip-rules]
                           [--input-mapping-default-values]
                           [--input-mapping-fields]
                           [--input-schema {cloudeventschemav1_0, customeventschema, eventgridschema}]
                           [--public-network-access {disabled, enabled}]
                           [--sku {basic, premium}]
                           [--tags]. The 1th example of the child command would be to use it to 'create a new domain', the syntax is: az eventgrid domain create -g rg1 --name domain1 -l westus2. The 2th example of the child command would be to use it to 'create a new domain with custom input mappings', the syntax is: az eventgrid domain create -g rg1 --name domain1 -l westus2 --input-schema customeventschema --input-mapping-fields topic=mytopicField eventType=myEventTypeField --input-mapping-default-values subject=DefaultSubject dataVersion=1.0. The 3th example of the child command would be to use it to 'create a new domain that accepts events published in cloudevents v1 0 schema and maps a property mytopicfield to the topic name', the syntax is: az eventgrid domain create -g rg1 --name domain1 -l westus2 --input-schema cloudeventschemav1_0 --input-mapping-fields topic=mytopicfield. The 4th example of the child command would be to use it to 'create a new domain which allows specific inbound ip rules', the syntax is: az eventgrid domain create -g rg1 --name domain1 -l westus2 --public-network-access enabled --inbound-ip-rules 10.0.0.0/8 Allow --inbound-ip-rules 10.2.0.0/8 Allow --sku basic. The parameter '--location -l' is required. It is used to location. values from: `az account list-locations`. you can configure the default location using `az configure --defaults location=<location>`.. The parameter '--name -n' is required. It is used to name of the domain.. 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 '--identity' is optional. the identity type of the resource (e.g., topic or domain).. The parameter '--inbound-ip-rules' is optional. list of inbound ip rules.. The parameter '--input-mapping-default-values' is optional. when input-schema is specified as customeventschema, this parameter can be used to specify input mappings based on default values. you can use this parameter when your custom schema does not include a field that corresponds to one of the three fields supported by this parameter. specify space separated mappings in 'key=value' format. allowed key names are 'subject', 'eventtype', 'dataversion'. the corresponding value names should specify the default values to be used for the mapping and they will be used only when the published event doesn't have a valid mapping for a particular field.. The parameter '--input-mapping-fields' is optional. when input-schema is specified as customeventschema, this parameter is used to specify input mappings based on field names. specify space separated mappings in 'key=value' format. allowed key names are 'id', 'topic', 'eventtime', 'subject', 'eventtype', 'dataversion'. the corresponding value names should specify the names of the fields in the custom input schema. if a mapping for either 'id' or 'eventtime' is not provided, event grid will auto-generate a default value for these two fields.. The parameter '--input-schema' is optional. schema in which incoming events will be published to this topic/domain. if you specify customeventschema as the value for this parameter, you must also provide values for at least one of --input_mapping_default_values / --input_mapping_fields.. The parameter '--public-network-access' is optional. this determines if traffic is allowed over public network. by default it is enabled. you can further restrict to specific ips by configuring.. The parameter '--sku' is optional. the sku name of the resource.. The parameter '--tags' is optional. space-separated tags: key[=value] [key[=value] ...]. use "" to clear existing tags.. 