Add Microsoft Office 2024 to version 10.0.60917

[pkunze]

Updated the version entry for 10.0.60917 to include Microsoft Office 2024.
As per our experience, VSTO works just fine with Microsoft Office 2024 but our customers security evaluation raises concerns, since the support is not officially documented.

If Microsoft Office 2024 is supported, it would be great if this would be included in the support schedule.

[prmerger-automator]

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

[learn-build-service-prod]

Learn Build status updates of commit fce6560:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/vsto/visual-studio-tools-for-office-runtime.md	✅Succeeded

For more details, please refer to the build report.

[Copilot]

Pull request overview

Updates the VSTO Runtime version support table to explicitly list Microsoft Office 2024 as supported for the VSTO Runtime release 10.0.60917, aligning the documentation with reported customer expectations around Office 2024 compatibility.

Changes:

• Added Microsoft Office 2024 to the “Microsoft Office version” column for VSTO Runtime 10.0.60917 (02/28/2024).

[Diana Richards (v-dirichards)]

Bill Wagner (@BillWagner)

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]

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

[chcomley (chcomley)]

pkunze
Thank you for raising this documentation gap. I've confirmed that VSTO Runtime version 10.0.60917 was released on February 28, 2024, before Office LTSC 2024 and Office 2024 became available. Under the published VSTO lifecycle policy, a downloadable runtime follows the lifecycle of the latest Office version available when that runtime was released. The current documentation therefore associates version 10.0.60917 with Office 2019, Office 2021, and Office 365, but not Office 2024.

Although VSTO solutions compatible with Office 2021 are generally expected to work with Office 2024, compatibility does not establish that this runtime version follows the Office 2024 support lifecycle. Adding Office 2024 to this table would require explicit confirmation from the VSTO or Office servicing team.

I’ve tagged the article PM (pkunze) , who can comment if the support policy has changed. We can update the documentation at that point if needed. For now, I'm closing this PR without merging the proposed change. Thank you for contributing.
RoseHJM FYI

[pkunze]

I think the documentation should be revisited because to me it does not seem to have been up to date at the time of the latests VSTO release. E.g. the table in question lists Office 365, even though Office 365 had been rebranded to Microsoft 365 years before the latest VSTO Runtime was released in 2024.

In other words, the support matrix was already not fully aligned with the current Office product naming and release landscape at the time of the runtime release. This suggests the documentation may not have been comprehensively reconciled with Office releases and branding changes in the first place (even though I understand that Office 2024 has been released some months later).

Also: listing Office 365 (or Microsoft 365 for that matter) in the support-matrix suggests, that VSTO supports products that continued to evolve beyond the runtime release dates, yet Office 365 remains listed as a supported Office platform without limiting support to certain builds of Office 365 for example.

For that reason, I do not think the fact that the runtime predates Office 2024 is sufficient on its own to conclude that Office 2024 is unsupported. Instead, I would appreciate clarification from the product team regarding the actual support and, if necessary, a reconciliation of the support matrix to reflect current Office products and naming consistently.

I would be glad to read the thoughts of RoseHJM on this issue.

[chcomley (chcomley)]

pkunze I understand your point and am reopening the PR. Thank you.

[learn-build-service-prod]

Learn Build status updates of commit fce6560:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/vsto/visual-studio-tools-for-office-runtime.md	✅Succeeded

For more details, please refer to the build report.

[chcomley (chcomley)]

#sign-off

[prmerger-automator]

Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. John Hart (@John-Hart)

[chcomley (chcomley)]

https://github.com/John-Hart

[chcomley (chcomley)]

Thanks, pkunze. We're planning a broader refresh of several articles in the near future and will address this change as part of that effort. I'll close this PR for now. We appreciate your contribution.