Azure中如何实现Excel.Interop Services？App Service部署后能否保留原代码？

Great question! Let's break this down clearly since Excel Interop has critical limitations in Azure App Service that you need to know about.

1. Can you implement Excel Interop Services in Azure App Service? #

Short answer: No, you can't use Excel Interop directly in Azure App Service. Here's why:

• Excel Interop depends on a full desktop installation of Microsoft Office, which isn't present in the Azure App Service sandbox environment.
• The App Service sandbox restricts running desktop applications and COM components (which Interop relies on). Even if you tried to manually install Office, it wouldn't function reliably (or at all) in this environment.

Instead, use server-side, Office-free libraries built for cloud compatibility. Top options include:

• Open XML SDK: Microsoft's official library for manipulating Office files (Excel, Word, PowerPoint) without needing Office installed. Ideal for low-level work with .xlsx/.xlsm files.
• EPPlus: A lightweight, open-source library focused on Excel files, with an intuitive API for reading, writing, and formatting spreadsheets.
• NPOI: An open-source library supporting both legacy .xls and modern .xlsx formats, compatible with all .NET versions.

Quick example with EPPlus (reading an Excel cell):

using OfficeOpenXml;

// Set license context (required for commercial use)
ExcelPackage.LicenseContext = LicenseContext.NonCommercial;

using (var package = new ExcelPackage(new FileInfo(@"path/to/your/file.xlsx")))
{
    var worksheet = package.Workbook.Worksheets.First();
    var cellValue = worksheet.Cells["A1"].Value?.ToString();
    Console.WriteLine(cellValue);
}

If you absolutely need to use Excel Interop (e.g., for complex macros or niche Office features), consider Azure Virtual Machines (VMs) instead. On a VM, you can install the full Microsoft Office desktop suite, deploy your app, and run Interop code just like you would on-premises. Keep in mind this adds more management overhead and cost compared to App Service.

2. Can you retain your existing Excel Interop code when deploying to Azure? #

Unfortunately, no—your existing Interop code won't work in Azure App Service. You'll need to refactor your code to use one of the Office-free libraries mentioned above.

The good news is that most common Excel operations (reading/writing cells, formatting, creating basic charts) have equivalent functionality in these libraries. You can test the refactored code locally first to ensure it matches your original behavior, then deploy to Azure with confidence.

内容的提问来源于stack exchange，提问作者NidhiThomas