Skip to content

Conversation

@ronking-zhu
Copy link
Contributor

Task schedule cannot not run to create the folder in azure vm temporary disk because of security reason.

Task schedule cannot not run to create the folder in azure vm temporary disk because of security reason.
@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit 0bbd44a:

✅ Validation status: passed

File Status Preview URL Details
azure-sql/virtual-machines/windows/tempdb-ephemeral-storage.md ✅Succeeded

For more details, please refer to the build report.

@prmerger-automator
Copy link
Contributor

@ronking-zhu : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@prmerger-automator
Copy link
Contributor

@ronking-zhu : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR addresses a security-related issue where task schedules cannot run to create folders on Azure VM temporary disks. The update adds documentation guidance for properly configuring scheduled task security options.

Key Changes:

  • Adds instructions to manually test the scheduled task after creation
  • Includes security configuration guidance for tasks created by normal users

1. Review the summary on the **Finish** tab and select **Finish** to create the task:

:::image type="content" source="media/tempdb-ephemeral-storage/create-sql-start-task.png" alt-text="Screenshot of the Task Scheduler, Create a Basic Task window, showing where to enter the script path.":::
---- Whenever you finish the creation of the task, be sure to manaully start to test run. If you are using normal user to create the task schedule, be sure to configure Security options as below.
Copy link

Copilot AI Dec 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Corrected spelling of 'manaully' to 'manually'.

Suggested change
---- Whenever you finish the creation of the task, be sure to manaully start to test run. If you are using normal user to create the task schedule, be sure to configure Security options as below.
---- Whenever you finish the creation of the task, be sure to manually start to test run. If you are using normal user to create the task schedule, be sure to configure Security options as below.

Copilot uses AI. Check for mistakes.
1. Review the summary on the **Finish** tab and select **Finish** to create the task:

:::image type="content" source="media/tempdb-ephemeral-storage/create-sql-start-task.png" alt-text="Screenshot of the Task Scheduler, Create a Basic Task window, showing where to enter the script path.":::
---- Whenever you finish the creation of the task, be sure to manaully start to test run. If you are using normal user to create the task schedule, be sure to configure Security options as below.
Copy link

Copilot AI Dec 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The line begins with four hyphens (----), which is invalid Markdown syntax. Use three hyphens (---) for a horizontal rule, or remove the hyphens if they're unintended.

Suggested change
---- Whenever you finish the creation of the task, be sure to manaully start to test run. If you are using normal user to create the task schedule, be sure to configure Security options as below.
Whenever you finish the creation of the task, be sure to manaully start to test run. If you are using normal user to create the task schedule, be sure to configure Security options as below.

Copilot uses AI. Check for mistakes.
1. Review the summary on the **Finish** tab and select **Finish** to create the task:

:::image type="content" source="media/tempdb-ephemeral-storage/create-sql-start-task.png" alt-text="Screenshot of the Task Scheduler, Create a Basic Task window, showing where to enter the script path.":::
---- Whenever you finish the creation of the task, be sure to manaully start to test run. If you are using normal user to create the task schedule, be sure to configure Security options as below.
Copy link

Copilot AI Dec 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The sentence structure is unclear. Consider revising to: 'After you finish creating the task, manually start it to test. If you're creating the task schedule as a normal user, configure the Security options as shown below.'

Suggested change
---- Whenever you finish the creation of the task, be sure to manaully start to test run. If you are using normal user to create the task schedule, be sure to configure Security options as below.
After you finish creating the task, manually start it to test. If you're creating the task schedule as a normal user, configure the **Security options** as shown below.

Copilot uses AI. Check for mistakes.

:::image type="content" source="media/tempdb-ephemeral-storage/create-sql-start-task.png" alt-text="Screenshot of the Task Scheduler, Create a Basic Task window, showing where to enter the script path.":::
---- Whenever you finish the creation of the task, be sure to manaully start to test run. If you are using normal user to create the task schedule, be sure to configure Security options as below.
<img width="1224" height="925" alt="image" src="https://github.com/user-attachments/assets/d7f6d37d-5177-4a82-a35d-de5ac76b04f5" />
Copy link

Copilot AI Dec 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Use the standard Learn Markdown image syntax with :::image::: instead of HTML tags to maintain consistency with the rest of the documentation. The alt text should also be more descriptive than 'image'. Example: ':::image type="content" source="path/to/image.png" alt-text="Screenshot of Task Scheduler security options configuration":::'

Copilot uses AI. Check for mistakes.

:::image type="content" source="media/tempdb-ephemeral-storage/create-sql-start-task.png" alt-text="Screenshot of the Task Scheduler, Create a Basic Task window, showing where to enter the script path.":::
---- Whenever you finish the creation of the task, be sure to manaully start to test run. If you are using normal user to create the task schedule, be sure to configure Security options as below.
<img width="1224" height="925" alt="image" src="https://github.com/user-attachments/assets/d7f6d37d-5177-4a82-a35d-de5ac76b04f5" />
Copy link

Copilot AI Dec 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The alt text 'image' is not descriptive enough for accessibility. Replace with descriptive text such as 'Screenshot showing Task Scheduler security options for configuring user permissions'.

Suggested change
<img width="1224" height="925" alt="image" src="https://github.com/user-attachments/assets/d7f6d37d-5177-4a82-a35d-de5ac76b04f5" />
<img width="1224" height="925" alt="Screenshot of the Task Scheduler Security options dialog showing configuration for running the task with the highest privileges and a specific user account." src="https://github.com/user-attachments/assets/d7f6d37d-5177-4a82-a35d-de5ac76b04f5" />

Copilot uses AI. Check for mistakes.
@ktoliver
Copy link
Contributor

@dplessMSFT

Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label Dec 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants