> For the complete documentation index, see [llms.txt](https://docs.duplocloud.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplocloud.com/docs/automation-platform/overview-2/use-cases/azure-maintenance-schedules.md). # Azure Maintenance Schedules Manage Azure maintenance schedules from the DuploCloud Portal DuploCloud allows you to configure maintenance schedules for Azure hosts to control when automated platform operations can occur, minimizing downtime during critical business hours. You can create or update a maintenance schedule directly from the DuploCloud Portal for each individual host. ## Creating a Maintenance Schedule 1. In the DuploCloud Portal, navigate to **Cloud Services** -> **Hosts**. 2. Select the tab matching the type of host you want to configure a maintenance schedule for (**Host** or **VM Scale Set**. 3. Click on the host name in the **NAME** column. 4. Select the **Maintenance Schedule** tab. 5. If no schedule is currently configured, click **Enable Maintenance Schedule**.\ The **Create VM Maintenance Schedule** pane displays.

6. Complete the following fields:


Start Time	Specify the date and time when the maintenance window begins, for example, 2025-06-15 01:00 PM. Choose a time window that aligns with your application’s low-traffic periods to minimize potential impact.
Time Zone	Select the time zone used for scheduling.
Maintenance window (Hours/Minutes)	Specify the number of hours and minutes the window should last (e.g., 1 hour, 30 minutes).
Repeats	Define the recurrence pattern by specifying a number and frequency: • Day: Repeats every N days. • Week: Prompts you to select one or more weekdays. • Month: Prompts you to choose specific dates and/or weekday occurrences.
Repeats on	If needed (if Weekly or Monthly repeats are selected), specify the repeat frequency: • For Weekly, select one or more days (e.g., Monday). • For Monthly, choose dates (e.g., 5, 20) or weekday occurrences (e.g., 3rd Friday).
End Time	Optionally, specify the date and time when the recurring schedule should stop. For example, 2025-12-15 01:00 PM.

7. Click **Save** to activate the schedule. The new schedule appears in the **Maintenance Schedule** tab.

## Updating a Maintenance Schedule You can modify an existing maintenance schedule at any time using the host settings. 1. In the DuploCloud Portal, navigate to **Cloud Services** -> **Hosts**. 2. Select the tab that matches the type of host you want to update a maintenance schedule for (**Host** or **VM Scale Set**. 3. Click on the host name in the **NAME** column to open the host details page. 4. Click the **Actions** menu**,** select **Host Settings**, and then **Update Maintenance Schedule**. The **Update VM Maintenance Schedule** pane displays, pre-filled with the current settings.

5. Modify any of the fields listed in the **Update VM Maintenance Schedule** pane (also listed in the table above).

6. Click **Save** to apply your changes. Changes may take a few minutes to propagate across Azure systems. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.duplocloud.com/docs/automation-platform/overview-2/use-cases/azure-maintenance-schedules.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.