You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/virtual-machines/azure-compute-gallery.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ An Azure Compute Gallery helps you build structure and organization around your
26
26
27
27
With a gallery, you can share your resources to everyone, or limit sharing to different users, service principals, or AD groups within your organization. Resources can be replicated to multiple regions, for quicker scaling of your deployments.
28
28
29
-
<sup>1</sup> The Azure Compute Gallery service isn't a global resource. For disaster recovery scenarios, it's a best practice is to have at least two galleries, in different regions.
29
+
<sup>1</sup> The Azure Compute Gallery service isn't a global resource. For disaster recovery scenarios, the best practice is to have at least two galleries, in different regions.
Copy file name to clipboardExpand all lines: articles/virtual-machines/create-gallery.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -115,6 +115,8 @@ PUT https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{
115
115
>
116
116
> You can't currently create a Flexible virtual machine scale set from an image shared to you by another tenant.
117
117
118
+
To start sharing a direct shared gallery with a subscription or tenant, use see [Share a gallery with a subscription or tenant](./share-gallery-direct.md).
119
+
118
120
### [Portal](#tab/portaldirect)
119
121
120
122
1. Sign in to the Azure portal at https://portal.azure.com.
@@ -181,7 +183,7 @@ POST https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/
181
183
182
184
---
183
185
184
-
To start sharing the gallery with a subscription or tenant, use see [Share a gallery with a subscription or tenant](./share-gallery-direct.md).
Copy file name to clipboardExpand all lines: articles/virtual-machines/image-version.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,8 +13,6 @@ ms.custom:
13
13
14
14
---
15
15
16
-
17
-
18
16
# Create an image definition and an image version
19
17
20
18
A [Azure Compute Gallery](shared-image-galleries.md) (formerly known as Shared Image Gallery) simplifies custom image sharing across your organization. Custom images are like marketplace images, but you create them yourself. Images can be created from a VM, VHD, snapshot, managed image, or another image version.
@@ -323,6 +321,8 @@ PUT https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{
323
321
}
324
322
```
325
323
324
+
---
325
+
326
326
## Create an image in one tenant using the source image in another tenant
327
327
328
328
In the subscription where the source image exists, grant reader permissions to the user. Once the user has reader permission to the source image, login to both accounts (source and target).
Make sure the state of the image is `Generalized`. If you want to use an image with the `Specialized` state, see [Create a VM from a specialized image version](vm-specialized-image-version.md).
740
740
741
-
Use the `Id` from the output, appended with `/Versions/latest` to use the latest version, as the value for `--image`` to create a VM. In this example, we are creating a VM from a Linux image that is directly shared to us, and creating SSH keys for authentication.
741
+
Use the `Id` from the output, appended with `/Versions/latest` to use the latest version, as the value for `--image` to create a VM. In this example, we are creating a VM from a Linux image that is directly shared to us, and creating SSH keys for authentication.
> **Known issue**: In the Azure portal, if you you select a region, select an image, then change the region, you will get an error message: "You can only create VM in the replication regions of this image" even when the image is replicated to that region. To get rid of the error, select a different region, then switch back to the region you want. If the image is available, it should clear the error message.
832
832
>
833
-
> You can also use the Azure CLI to check what images are shared with you. For example, you can use `az sig list-shared --location westus" to see what images are shared with you in the West US region.
833
+
> You can also use the Azure CLI to check what images are shared with you. For example, you can use `az sig list-shared --location westus` to see what images are shared with you in the West US region.
834
834
835
835
1. Type **virtual machines** in the search.
836
836
1. Under **Services**, select **Virtual machines**.
Copy file name to clipboardExpand all lines: articles/virtual-machines/vm-specialized-image-version.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -159,7 +159,7 @@ Now you can create one or more new VMs. This example creates a VM named *myVM*,
159
159
1. For **Availability options**, leave the default of *No infrastructure redundancy required*.
160
160
1. The value for **Image** is automatically filled with the `latest` image version if you started from the page for the image definition.
161
161
1. For **Size**, choose a VM size from the list of available sizes and then choose **Select**.
162
-
1. Under **Administrator account**, the username is greyed out because the username and credentials from the source VM are used.
162
+
1. Under **Administrator account**, the username is grayed out because the username and credentials from the source VM are used.
163
163
1. If you want to allow remote access to the VM, under **Public inbound ports**, choose **Allow selected ports** and then select **SSH (22)** or **RDP (3389)** from the drop-down. If you don't want to allow remote access to the VM, leave **None** selected for **Public inbound ports**.
164
164
1. When you're finished, select the **Review + create** button at the bottom of the page.
165
165
1. After the VM passes validation, select **Create** at the bottom of the page to start the deployment.
@@ -169,7 +169,7 @@ Now you can create one or more new VMs. This example creates a VM named *myVM*,
169
169
170
170
If the subscription where the gallery resides is within the same tenant, images shared through RBAC can be used to create VMs using the CLI and PowerShell.
171
171
172
-
You'll need to the `imageID` of the image you want to use and you need to make sure it is replicated to the region where you want to create the VM.
172
+
You'll need the `imageID` of the image you want to use and make sure the image is replicated to the region where you want to create the VM.
173
173
174
174
### [CLI](#tab/cli2)
175
175
@@ -266,7 +266,7 @@ New-AzVM `
266
266
267
267
If the image you want to use is stored in a gallery that isn't in the same tenant (directory) then you will need to sign in to each tenant to verify you have access.
268
268
269
-
You will need to the `imageID` of the image you want to use and you need to make sure it is replicated to the region where you want to create the VM. You will also need the `tenantID` for the source gallery and the `tenantID` for where you want to create the VM.
269
+
You'll need the `imageID` of the image you want to use and make sure the image is replicated to the region where you want to create the VM. You'll also need the `tenantID` for the source gallery and the `tenantID` for where you want to create the VM.
0 commit comments