Skip to content

Add Microsoft Office 2024 to version 10.0.60917 - #11416

Open
pkunze wants to merge 1 commit into
MicrosoftDocs:mainfrom
pkunze:patch-1
Open

Add Microsoft Office 2024 to version 10.0.60917#11416
pkunze wants to merge 1 commit into
MicrosoftDocs:mainfrom
pkunze:patch-1

Conversation

@pkunze

@pkunze pkunze commented Aug 5, 2026

Copy link
Copy Markdown

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.

Updated the version entry for 10.0.60917 to include Microsoft Office 2024.
@prmerger-automator

Copy link
Copy Markdown
Contributor

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

Copy link
Copy Markdown
Contributor

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 AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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).

@v-dirichards

Copy link
Copy Markdown
Contributor

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

Copy link
Copy Markdown
Contributor

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

@prmerger-automator prmerger-automator Bot added the aq-pr-triaged tracking label for the PR review team label Aug 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants