-
Notifications
You must be signed in to change notification settings - Fork 187
[AutoPublish] main to live - 10/08 01:36 PDT | 10/08 14:06 IST #1053
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
Conversation
… to Set-SPOTenant
Updated example command and explanation for Add-SPOContainerTypeBilling.
Updated example command with a new container ID.
Updated the ContainerId in Example 1 to a new value.
Updated example in Set-SPOContainerUser.md to use a new container ID.
Updated example in Get-SPOContainerType.md to reflect new ContainerTypeId.
Updated OwningApplicationId values in examples for New-SPOContainerType.
Updated example commands in Get-SPOApplication.md with specific OwningApplicationId and ApplicationId values.
Updated the ContainerTypeId in Example 6 to include a new identifier.
…nantUpdatesForAgents Update Set-SPOTenant with two new properties and four new parameters
Update examples on all SPE cmdlets
Refine examples in Get-SPOApplication.md
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 issues. Other issues are also a high priority. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
@MicrosoftDocs/marveldocs-pubops
This is an automated pull request to publish changes from the main branch to the live branch. Merging this PR will publish the changes to the live learn.microsoft.com site.
Auto-merge is enabled. The repo will attempt to automatically merge this PR when all required checks pass. If the PR is automatically merged, no further action is required to publish the contents of this PR.
In the event the repo can't automatically merge this PR, the Manual merge required label will be added to the PR. If this happens, complete the following checks before merging this PR:
After you've completed these steps, manually merge the PR.
If you have questions, post a message to https://aka.ms/askanadmin.