Retiring the ability to create Microsoft Application Virtualization (App-V) packages for Microsoft 365 Apps

Originally posted by Microsoft Nov 5, 2025 Uncategorized 0 Comments

Microsoft will retire the ability to create App-V packages for Microsoft 365 Apps starting January 13, 2026, focusing on Click-to-Run deployment instead. Existing App-V packages will still work, but new ones cannot be created with updated tools. Organizations should transition to Click-to-Run before this date.

Introduction

We’re retiring the ability to create App-V packages for Microsoft 365 Apps starting January 13, 2026. This change aligns with our focus on modern deployment methods and continued investment in Click-to-Run, which offers improved performance, reliability, and supportability.

What is App-V?

When this will happen:

This change will take effect on January 13, 2026. After this date, new versions of the Office Deployment Tool will no longer support App-V packaging for Microsoft 365 Apps.

How this affects your organization:

  • Who is affected: Organizations that use the Office Deployment Tool in packager mode to create App-V packages for Microsoft 365 Apps.
  • What will happen:
    • The Office Deployment Tool will no longer support creation of App-V packages using the /packager argument after January 13, 2026. (Example: setup.exe /packager packageconfig.xml)
    • Existing App-V packages will continue to function, but no new packages can be created using updated tools.
    • Organizations using Click-to-Run are not affected.
    • No changes will occur for organizations that do not use App-V for deployment.

What you can do to prepare:

  • Review your deployment strategy before January 13, 2026.
  • Transition to Click-to-Run deployment, which remains fully supported.
  • Update internal documentation and deployment scripts to reflect this change.
  • Communicate this change to IT and helpdesk teams.
  • Learn more about Click-to-Run deployment: Create an App-V package for Microsoft 365 Apps

Compliance considerations:

No compliance considerations identified, review as appropriate for your organization.

Message ID: MC1183012

Comments are closed.

Joao Ferreira

I've been working with Microsoft Technologies over the last ten years, mainly focused on creating collaboration and productivity solutions that drive the adoption of Microsoft Modern Workplace.

%d bloggers like this: