MicrosoftDocs
The page should state that the VM will be stopped.
[Enter feedback here] The page should state with a warning that the VM will be stopped. I took down a prod server because it doesn't say that.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
- ID: 3dfa7214-78bc-d8d9-bd29-8d465465e106
- Version Independent ID: 349d0c58-4fd9-5009-9f2b-f81761f733e9
- Content: Capture an image of a VM using the portal - Azure Virtual Machines
- Content Source: articles/virtual-machines/capture-image-portal.md
- Service: virtual-machines
- Sub-service: imaging
- GitHub Login: @cynthn
- Microsoft Alias: cynthn
@sjharper79 Thanks for your feedback! We will investigate and update as appropriate.
@sjharper79 I apologize for any inconvenience caused. The documentation you provided describes the process of capturing an image of a virtual machine in Azure using the Azure portal. However, I understand that the documentation may not have explicitly mentioned the fact that the virtual machine will be stopped during the image capture process.
When capturing an image of a virtual machine in Azure, it's important to note that the virtual machine will be temporarily stopped to ensure data consistency and prevent any potential issues during the image creation. This is because capturing an image requires a point-in-time snapshot of the virtual machine's disk.
To avoid unexpected disruptions in a production environment, it's recommended to schedule the image capture process during a maintenance window or a time when the temporary downtime can be accommodated without impacting critical services.
@cynthn Can you please check and add your comments on this doc update request as applicable.
@sjharper79 I have reached out to content author to update the document as per your request. if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.
@sjiang26 Thanks for reporting this! We have created a PR for this issue and the changes should go live soon.