Skip to content

docs: Intune sprint 2611 beta API updates - #10104

Draft
kajalpatel-msft wants to merge 1 commit into
microsoftgraph:mainfrom
kajalpatel-msft:kajalp-microsoft-2611-docs-for-pr-18017388
Draft

kajalpatel-msft wants to merge 1 commit into
microsoftgraph:mainfrom
kajalpatel-msft:kajalp-microsoft-2611-docs-for-pr-18017388

Conversation

@kajalpatel-msft

Copy link
Copy Markdown

Important

Use the AI-powered workflow for Graph onboarding to author and self-review schema-related changes. See https://aka.ms/msgraphcdk for more information.

Required for API changes:


Add other supporting information, such as a description of the PR changes:

Summary

Draft documentation for the public Intune beta changes in schema commit e7cc100b62b48cb8f5dbb14cc12b1d07f82dfac2, compared with 277afe438049f38f518dbdc1680a068b3979fb42:

  • Document read-only userPFXCertificate.keyAlgorithm and its enum, including legacy unknown/null/omitted values.
  • Document read-only Cloud PKI leaf-certificate algorithm, key size/curve, and signature hashing properties. Align the touched GET/List permission tables with the existing Cloud CA permissions in the API design; no new permission is introduced.
  • Document the deploymentPlan, deployment, and unknownFutureValue assignment payload enum members and synchronize the payloadByFilter value list.
  • Document Android work-profile app inventory configuration, including the default false, unchanged value when omitted from PATCH, and exclusion of personal-profile apps.
  • Update the relevant HTTP examples, beta disclaimers, property ordering, Intune changelog, and November 2026 preview What's New entries. Preserve existing topic paths; no duplicate resources or new endpoints are introduced.

Draft and publication gates

This PR must remain draft. The source schema PR is active/draft, not merged or deployed. Its recorded full-schema validation still has 14 Review/Prod mismatch errors, 7 warnings, and 8 breaking-change findings. This documentation does not resolve those gates or establish deployment/publication readiness.

WinGet repository changes are deliberately excluded because public-beta authorization remains unresolved; this PR does not claim complete coverage of that gated surface. Hidden-only changes, routing pins, and the unapproved top-level Cloud PKI version collection are also excluded.

Validation and self-review

  • Required authoring validator, & $validator -Files $files: passed for all 15 modified Markdown files ($validator is the installed docs-authoring\scripts\validate_authored_docs.ps1; $files contains only the assigned Markdown paths).
  • python C:\Kajal_Tracking\Graph\Sprint-2611-PE-Beta\Documentation\validate-2611.py: passed against seven pinned Prod Beta CSDLs. Checks cover property/enum parity, preservation of existing values, ten JSON examples, read-only fields, Android privacy/default/PATCH semantics, exclusions, local links, and four changelog records containing ten changes.
  • Get-Content changelog\Microsoft.Intune.json -Raw -Encoding UTF8 | Test-Json -SchemaFile changelog\Changelog.Schema.json: passed.
  • .\scripts\validate-changelog-json.ps1: passed for all 121 changelog files.
  • git -c core.longpaths=true diff --check -- api-reference/beta/api api-reference/beta/resources changelog/Microsoft.Intune.json concepts/whats-new-overview.md: passed.
  • The supported check-csdl-visibility.ps1 helper verified 178 documented symbol records against pinned-source snapshots: zero hidden and zero unresolved symbols, including inherited navigation declarations and enum values.

Read-only self-review was performed in the same session, not by an independent reviewer. It corrected explicit property naming in What's New, PFX nullability wording, example metadata/stale lengths, and the single-object GET response shapes. No agents, extra sessions, tracking work items, or generated SDK snippet changes are included.

API Doctor and upstream GitHub Actions have not been run locally; their results are not implied by the focused checks.


Important

The following guidance is for Microsoft employees only. Community contributors can ignore this message; our content team will manage the status.

After you've created your PR, expand this section for tips and additional instructions.
  • do not merge is the default PR status and is automatically added to all open PRs that don't have the ready to merge label.
  • Add the ready for content review label to start a review. Only PRs that have met the minimum requirements for content review and have this label are reviewed.
  • If your content reviewer requests changes, review the feedback and address accordingly as soon as possible to keep your pull request moving forward. After you address the feedback, remove the changes requested label, add the review feedback addressed label, and select the Re-request review icon next to the content reviewer's alias. If you can't add labels, add a comment with #feedback-addressed to the pull request.
  • After the content review is complete, your reviewer will add the content review complete label. When the updates in this PR are ready for external customers to use, replace the do not merge label with ready to merge and the PR will be merged within 24 working hours.
  • Pull requests that are inactive for more than 6 weeks will be automatically closed. Before that, you receive reminders at 2 weeks, 4 weeks, and 6 weeks. If you still need the PR, you can reopen or recreate the request.

For more information, see the Content review process summary.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@microsoft-github-policy-service

Copy link
Copy Markdown
Contributor

kajalpatel-msft please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

  • (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.
@microsoft-github-policy-service agree
  • (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.
@microsoft-github-policy-service agree company="Microsoft"
Contributor License Agreement

Contribution License Agreement

This Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
and conveys certain license rights to Microsoft Corporation and its affiliates (“Microsoft”) for Your
contributions to Microsoft open source projects. This Agreement is effective as of the latest signature
date below.

  1. Definitions.
    “Code” means the computer software code, whether in human-readable or machine-executable form,
    that is delivered by You to Microsoft under this Agreement.
    “Project” means any of the projects owned or managed by Microsoft and offered under a license
    approved by the Open Source Initiative (www.opensource.org).
    “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
    Project, including but not limited to communication on electronic mailing lists, source code control
    systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
    discussing and improving that Project, but excluding communication that is conspicuously marked or
    otherwise designated in writing by You as “Not a Submission.”
    “Submission” means the Code and any other copyrightable material Submitted by You, including any
    associated comments and documentation.
  2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any
    Project. This Agreement covers any and all Submissions that You, now or in the future (except as
    described in Section 4 below), Submit to any Project.
  3. Originality of Work. You represent that each of Your Submissions is entirely Your original work.
    Should You wish to Submit materials that are not Your original work, You may Submit them separately
    to the Project if You (a) retain all copyright and license information that was in the materials as You
    received them, (b) in the description accompanying Your Submission, include the phrase “Submission
    containing materials of a third party:” followed by the names of the third party and any licenses or other
    restrictions of which You are aware, and (c) follow any other instructions in the Project’s written
    guidelines concerning Submissions.
  4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else
    for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
    Submission is made in the course of Your work for an employer or Your employer has intellectual
    property rights in Your Submission by contract or applicable law, You must secure permission from Your
    employer to make the Submission before signing this Agreement. In that case, the term “You” in this
    Agreement will refer to You and the employer collectively. If You change employers in the future and
    desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
    and secure permission from the new employer before Submitting those Submissions.
  5. Licenses.
  • Copyright License. You grant Microsoft, and those who receive the Submission directly or
    indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
    Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
    the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
    parties.
  • Patent License. You grant Microsoft, and those who receive the Submission directly or
    indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
    Your patent claims that are necessarily infringed by the Submission or the combination of the
    Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
    import or otherwise dispose of the Submission alone or with the Project.
  • Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
    No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
    granted by implication, exhaustion, estoppel or otherwise.
  1. Representations and Warranties. You represent that You are legally entitled to grant the above
    licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
    have disclosed under Section 3). You represent that You have secured permission from Your employer to
    make the Submission in cases where Your Submission is made in the course of Your work for Your
    employer or Your employer has intellectual property rights in Your Submission by contract or applicable
    law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
    have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
    You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
    REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
    EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
    PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
    NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
  2. Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
    You later become aware that would make Your representations in this Agreement inaccurate in any
    respect.
  3. Information about Submissions. You agree that contributions to Projects and information about
    contributions may be maintained indefinitely and disclosed publicly, including Your name and other
    information that You submit with Your Submission.
  4. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
    the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
    Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
    exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
    defenses of lack of personal jurisdiction and forum non-conveniens.
  5. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
    supersedes any and all prior agreements, understandings or communications, written or oral, between
    the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.

@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit a5227fb:

⚠️ Validation status: warnings

File Status Preview URL Details
api-reference/beta/resources/intune-raimportcerts-userpfxcertificate.md ⚠️Warning Details
concepts/whats-new-overview.md ⚠️Warning Details
api-reference/beta/api/intune-cloudpkigraphservice-cloudcertificationauthorityleafcertificate-get.md ✅Succeeded
api-reference/beta/api/intune-cloudpkigraphservice-cloudcertificationauthorityleafcertificate-list.md ✅Succeeded
api-reference/beta/api/intune-deviceconfig-androidworkprofilegeneraldeviceconfiguration-create.md ✅Succeeded
api-reference/beta/api/intune-deviceconfig-androidworkprofilegeneraldeviceconfiguration-get.md ✅Succeeded
api-reference/beta/api/intune-deviceconfig-androidworkprofilegeneraldeviceconfiguration-list.md ✅Succeeded
api-reference/beta/api/intune-deviceconfig-androidworkprofilegeneraldeviceconfiguration-update.md ✅Succeeded
api-reference/beta/api/intune-raimportcerts-userpfxcertificate-get.md ✅Succeeded
api-reference/beta/api/intune-raimportcerts-userpfxcertificate-list.md ✅Succeeded
api-reference/beta/resources/enums.md ✅Succeeded
api-reference/beta/resources/intune-cloudpkigraphservice-cloudcertificationauthorityleafcertificate.md ✅Succeeded
api-reference/beta/resources/intune-deviceconfig-androidworkprofilegeneraldeviceconfiguration.md ✅Succeeded
api-reference/beta/resources/intune-policyset-associatedassignmentpayloadtype.md ✅Succeeded
api-reference/beta/resources/intune-policyset-payloadbyfilter.md ✅Succeeded
changelog/Microsoft.Intune.json ✅Succeeded

api-reference/beta/resources/intune-raimportcerts-userpfxcertificate.md

  • Line 28, Column 2: [Warning: file-not-found - See documentation] Invalid file link: '../api/intune-raimportcerts-userpfxcertificate-update.md'.

concepts/whats-new-overview.md

  • Line 49, Column 1: [Warning: duplicate-h2s - See documentation] Duplicate heading: 'H2 'November 2026: New in preview only''. Each second level heading (H2) in an article must be unique.
  • Line 94, Column 1: [Warning: duplicate-h2s - See documentation] Duplicate heading: 'H2 'November 2026: New in preview only''. Each second level heading (H2) in an article must be unique.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant