Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Limitation part about author's permission retention #325

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

LazaUK
Copy link
Contributor

@LazaUK LazaUK commented Mar 28, 2025

As per ICM # 603232905, job schedules require author to retain their permission even after managed identity assignment.

As per ICM # 603232905, job schedules require author to retain their permission even after managed identity assignment.
Copy link
Contributor

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

Copy link
Contributor

Learn Build status updates of commit d309a5e:

✅ Validation status: passed

File Status Preview URL Details
articles/machine-learning/how-to-schedule-pipeline-job.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@ttorble
Copy link
Contributor

ttorble commented Mar 28, 2025

@lgayhardt

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 C+L Pull Request Review Team label label Mar 28, 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