Choosing customer managed while creating the VM itself

Varma 1,385

is there any way that while creating the VM itself we can choose customer managed , if yes how?

AnuragSingh-MSFT 21,386 Reputation points

2024-05-09T12:26:28.4933333+00:00

@Varma, can you please share additional details regarding this questions? What is meant by "customer managed"? Please do share any reference link/article about it, to help us understand the scenario better.
Varma 1,385 Reputation points

2024-05-09T12:29:43.2633333+00:00

Hi Anurag,

We have patch orchestration modes with different types right?

so while creating the VM do we have option to choose "customer managed schedule" ?

1 answer

AnuragSingh-MSFT 21,386 Reputation points

2024-05-21T12:46:07.99+00:00
@Varma, thank you for providing additional details and apologies for the delayed response.

Yes, it can be set when creating the virtual machine. The following link should help you get more details about it:

Using Azure Portal - If you are using Azure portal to create VM, then the option to set "Patch Orchestration" type is available under Management tab at the bottom:

Using ARM - if you are using ARM template to create VM, the patch orchestrator type can be set using the PatchSettings parameter, as available here - Microsoft.Compute virtualMachines

Hope this helps.

If the answer did not help, please add more context/follow-up question for it. Else, if the answer helped, please click Accept answer so that it can help others in the community looking for help on similar topics.
Please sign in to rate this answer.
Varma 1,385 Reputation points

2024-05-21T12:49:36.8066667+00:00

Hi Anurag,

but manual update is not customer manged right ?

I am looking for patch orchestration has to be customer manager during vm creation , is it possible?

AnuragSingh-MSFT 21,386 Reputation points

2024-05-22T06:24:42.97+00:00

Varma, thank you for the reply.

Yes, you are right. Setting the "customer managed schedule" is not available when creating VM from portal. Instead, the steps is to select patch mode to "Azure-orchestrated" and then set it to "Customer Managed" from Azure Update Manager.

Or, you could use ARM template with the following settings when creating VM, which essentially means "Customer managed" schedule:

{ "location":"<location>", "properties": { "osProfile": { "windowsConfiguration": { "provisionVMAgent": true, "enableAutomaticUpdates": true, "patchSettings": { "patchMode": "AutomaticByPlatform", "automaticByPlatformSettings":{ "bypassPlatformSafetyChecksOnUserSchedule":true } } } } } }

For details, see Enable schedule patching on Azure VMs.

Hope this helps.

If the answer did not help, please add more context/follow-up question for it. Else, if the answer helped, please click Accept answer so that it can help others in the community looking for help on similar topics.

AnuragSingh-MSFT 21,386 Reputation points

2024-05-24T10:25:27.74+00:00

Varma, Following-up to check if you had a chance to review the answer provided.

If the answer did not help, please add more context/follow-up question for it. Else, if the answer helped, please click Accept answer so that it can help others in the community looking for help on similar topics.

Varma 1,385 Reputation points

2024-05-26T16:16:25.4266667+00:00

Hi Anurag,

Thank you for the response and follow up.

Please clarify my following follow up questions:

what exactly meany by azure orchestration below highlighted? why azure orchestration came in to picture when we are talking patch orchestration?

2.Do you mean using ARM template can we create the VM with customer managed?

3.what exactly Patch mode = Azure-orchestrated ?

4.and during VM creation if we select manual mode , does it mean we have to log in to the vm and then we apply patches apply , right? and we can not place that machine under maintenance configuration, am i right?

AnuragSingh-MSFT 21,386 Reputation points

2024-05-27T05:14:15.3933333+00:00

Varma, thank you for the reply. Please find below the response to your questions:

Patch Orchestration refers to the method used to apply patches to Azure virtual machines and Arc-enabled servers. It determines how the patches are applied and managed. **AutomaticByPlatform (**or Azure-orchestrated patching) means that the patching of the VMs is taken care by the Azure platform (considering some of the scenarios as mentioned here - Availability-first Updates). Azure orchestration in this case means that Azure will be coordinating among all the required components to get the patching done based on certain criteria.

Yes, based on the documentation.

Azure-orchestrated (or AutomaticByPlatform)'s details are available here - AutomaticByPlatform (Azure-orchestrated patching)

Yes, you are correct. Manual means that you would have to manually apply the updates. Neither Azure nor OS will apply the patch automatically/based on schedule.

Hope this helps.

If the answer helped, please click Accept answer so that it can help others in the community looking for help on similar topics.

Varma 1,385 Reputation points

2024-05-27T07:11:35.84+00:00

Hi Anurag,

1.

I am still not clear.

in patch orchestration - based on how we apply patches we determine patch mode, i got this

in azure orchestation ( automatic by platform ) , is it automatic, so this one is different from custom manged platform, am i correct?

so when we select VM as manual update while creating, even we place machine in mainteance configuraiton, it does not work as per schedule , am I correct?

AnuragSingh-MSFT 21,386 Reputation points

2024-05-27T08:26:30.4066667+00:00

Varma, to answer your questions:

Yes, the "Azure orchestrated" mode is different from the "Customer Managed" model.

Yes, it would not work. The prerequisite for schedule maintenance to work is that patch orchestrated mode should be "customer managed".

Hope this helps.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Choosing customer managed while creating the VM itself

1 answer

Your answer