Add missing OSLicense getter references

[Robin Harwood (robinharwood)]

PR Summary

Adds the two OSLicense getter reference pages omitted from the original module publication:

• Get-KmsLicenseInfo
• Get-SubscriptionLicenseInfo

The pages were authored manually against the engineering .psm1 sources and runtime Get-Command output. Microsoft.PowerShell.PlatyPS 1.0.3 couldn't generate these parameterless commands because Get-Help -Full exposes the empty parameter collection as System.String; PlatyPS then attempts to access .parameters.parameter in GetParameterDefaultValueFromHelp and throws a RuntimeBinderException.

The module page now links both commands. Static validation confirms schema 2024-05-01 heading order, canonical HelpUri metadata, common-parameter-only syntax, source-backed output properties, link integrity, and no AsJob parameter.

Related work:

• User Story 617456
• Original OSLicense reference: Add OSLicense PowerShell reference #4128
• Canonical help URI metadata: Use canonical OSLicense help URI metadata #4132

PR Checklist

• Descriptive Title: This PR's title is a synopsis of the changes it proposes.
• Summary: This PR's summary describes the scope and intent of the change.
• Contributor's Guide: I have read the contributors guide.
• Style: This PR adheres to the style guide.

[learn-build-service-prod]

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. 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 found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

[github-actions]

Robin Harwood (@robinharwood)
You have permissions to sign off pull requests in this repository. Reviewers will not be added to this PR.

Before this PR can be merged, you need to add the Sign off label to it. Before you sign off a PR, confirm the following:

• The PR is not in draft state. When the changes in this PR are ready to be published, select the Ready to merge button at the bottom of the page.
• Article content has been checked for technical accuracy.
• There are no errors or warnings in build validation.
• There are no severity 1 or 2 PoliCheck issues.
• All required PR checks at the bottom of the PR are passing.

After you've confirmed the above, do the following to sign off:

1. Select the gear next to Labels.
2. Select Sign off from the label list.
3. Click away from the label list.

After you've signed off, our operations (PubOps) team will review the PR for issues that may impact formatting and the customer experience. If any changes are needed, they will return
the PR to you with required changes. After they've completed those changes, you need to sign off again.

When the PR passes PubOps review, they'll merge the PR. If the PR is merged into the main branch, changes will go live within the next couple hours.

If you have questions about this process, or need help signing off on this PR, post a message to https://aka.ms/tcphelp.

[learn-build-service-prod]

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. 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 found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

[learn-build-service-prod]

Learn Build status updates of commit e310dc2:

✅ Validation status: passed

File	Status	Preview URL	Details
docset/winserver2025-ps/OSLicense/Get-KmsLicenseInfo.md	✅Succeeded	View (WindowsServer2025-ps)
docset/winserver2025-ps/OSLicense/Get-SubscriptionLicenseInfo.md	✅Succeeded	View (WindowsServer2025-ps)
docset/winserver2025-ps/OSLicense/OSLicense.md	✅Succeeded	View (WindowsServer2025-ps)

For more details, please refer to the build report.

[learn-build-service-prod]

Learn Build status updates of commit e6b778e:

✅ Validation status: passed

File	Status	Preview URL	Details
docset/winserver2025-ps/OSLicense/Get-KmsLicenseInfo.md	✅Succeeded	View (WindowsServer2025-ps)
docset/winserver2025-ps/OSLicense/Get-SubscriptionLicenseInfo.md	✅Succeeded	View (WindowsServer2025-ps)
docset/winserver2025-ps/OSLicense/OSLicense.md	✅Succeeded	View (WindowsServer2025-ps)

For more details, please refer to the build report.

[github-actions]

Robin Harwood (@robinharwood)
You have permissions to sign off pull requests in this repository. Reviewers will not be added to this PR.

Before this PR can be merged, you need to add the Sign off label to it. Before you sign off a PR, confirm the following:

• The PR is not in draft state. When the changes in this PR are ready to be published, select the Ready to merge button at the bottom of the page.
• Article content has been checked for technical accuracy.
• There are no errors or warnings in build validation.
• There are no severity 1 or 2 PoliCheck issues.
• All required PR checks at the bottom of the PR are passing.

After you've confirmed the above, do the following to sign off:

1. Select the gear next to Labels.
2. Select Sign off from the label list.
3. Click away from the label list.

After you've signed off, our operations (PubOps) team will review the PR for issues that may impact formatting and the customer experience. If any changes are needed, they will return
the PR to you with required changes. After they've completed those changes, you need to sign off again.

When the PR passes PubOps review, they'll merge the PR. If the PR is merged into the main branch, changes will go live within the next couple hours.

If you have questions about this process, or need help signing off on this PR, post a message to https://aka.ms/tcphelp.

[learn-build-service-prod]

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. 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 found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

[learn-build-service-prod]

Learn Build status updates of commit 91e01ae:

✅ Validation status: passed

File	Status	Preview URL	Details
docset/winserver2025-ps/OSLicense/Get-KmsLicenseInfo.md	✅Succeeded	View (WindowsServer2025-ps)
docset/winserver2025-ps/OSLicense/Get-SubscriptionLicenseInfo.md	✅Succeeded	View (WindowsServer2025-ps)
docset/winserver2025-ps/OSLicense/OSLicense.md	✅Succeeded	View (WindowsServer2025-ps)

For more details, please refer to the build report.

[github-actions]

Robin Harwood (@robinharwood)
You have permissions to sign off pull requests in this repository. Reviewers will not be added to this PR.

Before this PR can be merged, you need to add the Sign off label to it. Before you sign off a PR, confirm the following:

• The PR is not in draft state. When the changes in this PR are ready to be published, select the Ready to merge button at the bottom of the page.
• Article content has been checked for technical accuracy.
• There are no errors or warnings in build validation.
• There are no severity 1 or 2 PoliCheck issues.
• All required PR checks at the bottom of the PR are passing.

After you've confirmed the above, do the following to sign off:

1. Select the gear next to Labels.
2. Select Sign off from the label list.
3. Click away from the label list.

After you've signed off, our operations (PubOps) team will review the PR for issues that may impact formatting and the customer experience. If any changes are needed, they will return
the PR to you with required changes. After they've completed those changes, you need to sign off again.

When the PR passes PubOps review, they'll merge the PR. If the PR is merged into the main branch, changes will go live within the next couple hours.

If you have questions about this process, or need help signing off on this PR, post a message to https://aka.ms/tcphelp.

[learn-build-service-prod]

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. 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 found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

[learn-build-service-prod]

Learn Build status updates of commit e2fb151:

✅ Validation status: passed

File	Status	Preview URL	Details
docset/winserver2025-ps/OSLicense/Get-KmsLicenseInfo.md	✅Succeeded	View (WindowsServer2025-ps)
docset/winserver2025-ps/OSLicense/Get-SubscriptionLicenseInfo.md	✅Succeeded	View (WindowsServer2025-ps)
docset/winserver2025-ps/OSLicense/OSLicense.md	✅Succeeded	View (WindowsServer2025-ps)

For more details, please refer to the build report.