MicrosoftDocs
Update code example in pre-post-events-schedule-maintenance-configuration.md
Fix webhook creation code. Previously was using New-AzEventGridSystemTopicEventSubscription -Endpoint $PreEventWebhookEndpoint, but -Endpoint is no longer a valid parameter starting in Azure PowerShell 12.3.0 (was supported in Azure PowerShell 11.6.0) - https://learn.microsoft.com/en-us/powershell/module/az.eventgrid/new-azeventgridsystemtopiceventsubscription
@josh-martin-1 : Thanks for your contribution! The author(s) have been notified to review your proposed change.
![prmerger-automator[bot] avatar](https://avatars.githubusercontent.com/u/22479449?v=4 "Published by a pub.dev verified publisher"){kind=small}
Learn Build status updates of commit f582e20:
:bulb: Validation status: suggestions
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/update-manager/pre-post-events-schedule-maintenance-configuration.md | :bulb:Suggestion | Details |
articles/update-manager/pre-post-events-schedule-maintenance-configuration.md
- Line 142, Column 69: [Suggestion: preserve-view-not-set - See documentation]
You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /rest/api/maintenance/maintenance-configurations/create-or-update?view=rest-maintenance-2023-09-01-preview&tabs=HTTP
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
![learn-build-service-prod[bot] avatar](https://avatars.githubusercontent.com/in/237442?v=4 "Published by a pub.dev verified publisher"){kind=small}
@SnehaSudhirG 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
I sent an email to the content owner today.
@MicrosoftDocs/public-repo-pr-review-team
