Skip to content

Commit a5724d1

Browse files
Update articles/virtual-machines/security-isolated-image-builds-image-builder.md
Co-authored-by: Diana Richards <[email protected]>
1 parent bef2087 commit a5724d1

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/virtual-machines/security-isolated-image-builds-image-builder.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ Isolated Image Builds enable defense-in-depth by limiting network access of your
3030

3131
This is a platform level change and doesn't affect AIB's interfaces. So, your existing Image Template and Trigger resources continue to function and there's no change in the way you'll deploy new resources of these types. Similarly, customization logs continue to be available in the storage account.
3232

33-
You may observe a few new resources temporarily appear in the staging resource group (for example, Azure Container Instance, and Private Endpoint) while some other resource will no longer appear (for example, Public IP Address). Just as earlier, these temporary resources will exist only for the duration of the build and will be deleted by Image Builder thereafter.
33+
You might observe a few new resources temporarily appear in the staging resource group (for example, Azure Container Instance, and Private Endpoint) while some other resource will no longer appear (for example, Public IP Address). Just as earlier, these temporary resources will exist only for the duration of the build and will be deleted by Image Builder thereafter.
3434

3535
Your image builds will automatically be migrated to Isolated Image Builds and you need to take no action to opt-in.
3636

0 commit comments

Comments
 (0)