
.TH "GCLOUD_ACTIVE\-DIRECTORY_PEERINGS_CREATE" 1



.SH "NAME"
.HP
gcloud active\-directory peerings create \- create a Managed Microsoft Active Directory domain peering



.SH "SYNOPSIS"
.HP
\f5gcloud active\-directory peerings create\fR \fIPEERING\fR \fB\-\-authorized\-network\fR=\fIAUTHORIZED_NETWORK\fR \fB\-\-domain\fR=\fIDOMAIN\fR [\fB\-\-async\fR] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

Create a new Managed Microsoft AD domain peering with the given name using
Google Cloud's Managed Service for Microsoft Active Directory.

This command can fail for the following reasons:
.RS 2m
.IP "\(bu" 2m
A domain peering with the same name already exists.
.IP "\(bu" 2m
The active account does not have permission to create AD domains peerings.
.IP "\(bu" 2m
There is an overlap between the provided CIDR range and authorized network's
CIDR.
.RE
.sp



.SH "EXAMPLES"

The following command creates an AD domain peering with the name
\f5\fImy\-peering\fR\fR, network \f5\fImy\-network\fR\fR and domain
\f5\fIprojects/domain\-project/locations/global/domains/domain.com\fR\fR

.RS 2m
$ gcloud active\-directory peerings create my\-peering \e
    \-\-domain=projects/domain\-project/locations/global/domains/\e
domain.com \e
    \-\-authorized\-network=projects/network\-project/global/networks/\e
my\-network
.RE



.SH "POSITIONAL ARGUMENTS"

.RS 2m
.TP 2m

Peering resource \- Name of the managed Managed Microsoft AD domain peering you
want to create. This represents a Cloud resource. (NOTE) Some attributes are not
given arguments in this group but can be set in other ways.

To set the \f5project\fR attribute:
.RS 2m
.IP "\(em" 2m
provide the argument \f5peering\fR on the command line with a fully specified
name;
.IP "\(em" 2m
provide the argument \f5\-\-project\fR on the command line;
.IP "\(em" 2m
set the property \f5core/project\fR.
.RE
.sp

This must be specified.


.RS 2m
.TP 2m
\fIPEERING\fR

ID of the peering or fully qualified identifier for the peering.

To set the \f5peering\fR attribute:
.RS 2m
.IP "\(bu" 2m
provide the argument \f5peering\fR on the command line.
.RE
.sp


.RE
.RE
.sp

.SH "REQUIRED FLAGS"

.RS 2m
.TP 2m
\fB\-\-authorized\-network\fR=\fIAUTHORIZED_NETWORK\fR

Name of the Network that is authorized to communicate with Managed Microsoft AD
domain. This is usually the full path name of the network in the peer project.

.TP 2m
\fB\-\-domain\fR=\fIDOMAIN\fR

Name of the managed Managed Microsoft AD domain you want to peer to.


.RE
.sp

.SH "OPTIONAL FLAGS"

.RS 2m
.TP 2m
\fB\-\-async\fR

Return immediately, without waiting for the operation in progress to complete.


.RE
.sp

.SH "GCLOUD WIDE FLAGS"

These flags are available to all commands: \-\-access\-token\-file, \-\-account,
\-\-billing\-project, \-\-configuration, \-\-flags\-file, \-\-flatten,
\-\-format, \-\-help, \-\-impersonate\-service\-account, \-\-log\-http,
\-\-project, \-\-quiet, \-\-trace\-token, \-\-user\-output\-enabled,
\-\-verbosity.

Run \fB$ gcloud help\fR for details.



.SH "API REFERENCE"

This command uses the \fBmanagedidentities/v1\fR API. The full documentation for
this API can be found at: https://cloud.google.com/managed\-microsoft\-ad/



.SH "NOTES"

These variants are also available:

.RS 2m
$ gcloud alpha active\-directory peerings create
.RE

.RS 2m
$ gcloud beta active\-directory peerings create
.RE


