Others

How to Securely Publish a Microsoft Word Add-in to AppSource

Tauseeq Magsi Oct 10, 2026 869 views

Question details

The user needs to securely grant Microsoft reviewers access to a Word add-in submitted to AppSource, avoiding the use of shared permanent authentication tokens.

How to Securely Publish a Microsoft Word Add-in to AppSource

Product: Microsoft Word Add-ins
Device & OS: not provided
Scenario: Preparing to publish a Word add-in to Microsoft AppSource and setting up secure reviewer authentication.
Observed behavior: The user is seeking a secure alternative to shared permanent tokens for reviewer access during the submission process.

Before you start

Ensure you have access to your Microsoft Partner Center account and review the latest Microsoft 365 developer documentation regarding AppSource submission policies.

Solution 1Recommended

Provide Secure Test Credentials in Partner Center

The most secure and recommended method is to provide Microsoft reviewers with dedicated, temporary test credentials rather than hardcoding a token.

Microsoft strongly advises against using a shared permanent token solely for reviewers, as it poses a significant security risk. Instead, you should rely on standard, secure authentication protocols.

Create a restricted test tenant or account

Set up a dedicated test tenant or a test user account with least-privilege permissions specifically tailored for the review process. Do not use production accounts.

Configure OAuth-based sign-in

Implement standard OAuth-based authentication in your add-in using short-lived tokens. Ensure all authentication traffic is forced over HTTPS.

Submit credentials for review

During the AppSource submission process in the Microsoft Partner Center, enter the test account credentials in the 'Notes for certification' or reviewer notes section so Microsoft testers can log in normally.

Provide Secure Test Credentials in Partner Center

Security Best Practice: Always enforce HTTPS, utilize short-lived tokens, and ensure secure secret storage for your add-in's backend services.

Free Microsoft Office alternative

Develop and Edit Documents Efficiently with WPS Office

While publishing add-ins to AppSource is highly specific to the Microsoft ecosystem, if you need a lightweight, cost-effective solution for your daily document editing and testing needs, WPS Office provides a highly compatible and feature-rich environment.

1. Visit the official website: Go to the WPS Office official website to download the free installer.
2. Install the application: Run the lightweight installer and follow the on-screen instructions to set up WPS Office on your device.
3. Open your documents: Launch WPS Writer and seamlessly open, edit, and save your existing Word documents.

Fully compatible with Microsoft Word (.docx) formatsLightweight architecture for fast installation and operationFree to use for daily document processingFamiliar user interface requiring zero learning curve

microsoft office alternative - wps office

Frequently Asked Questions

Can I use a permanent token for AppSource reviewers?

No, using a shared permanent token is a security risk and strongly discouraged by Microsoft. Instead, use short-lived tokens and provide secure test account credentials.

Where do I provide the test credentials for my Word add-in?

You should provide the test account credentials in the Microsoft Partner Center during the add-in submission process, typically within the 'Notes for certification' section.

What authentication standards are required for Office Add-ins?

Office Add-ins should use standard OAuth-based sign-in flows over HTTPS, applying least-privilege permissions and short-lived tokens.

What should I do if my add-in requires access to specific tenant data?

Set up a restricted test tenant populated with sample data specifically for the reviewers, ensuring no sensitive or production data is exposed during the certification process.

Office Quick Solutions