Back to all updates

almost 7 years ago

How to provide testing access to your Office 365 App or Add-in

How's it going, productivity hackers?

We’re getting close to the submission deadline, so we wanted to remind you that in order to be eligible for prizes, you must include access to your App or Add-in with your Devpost submission.

Not sure how to provide access? We’ve got you covered.

--> For applications integrating one or more Office 365 APIs or Graph API

If this describes your application, then you’ve most likely created a web app, mobile app, or desktop app. Check out the full instructions (by platform) on how to share access with Devpost.

--> For newly created Office 365 Add-ins

If you’ve created an Office 365 Add-in for this competition, you’ve got two options.

Option 1: Add your Add-in to the Office Store

Essentially, this is comprised of two steps.

  1. Creating a Seller Dashboard account
  2. Getting the app validated by the AppSure team

For Store validation guidelines, policies & best practices, please refer to the following resources:

  1. Use the OACK test tool to make sure no basic manifest/app package errors exist.
  2. Have a partner conduct their own basic testing/QA to ensure performance & reliability are up to standard.
  3. Ensure Add-in best practices are followed:
  4. Follow the Office Store checklist & know Validation policies

Option 2: Send a Manifest File

If you don’t plan to release to the Office Store, then you will need to provide an app manifest for users/testers to side-load. Remember that you’ll need to make sure that a demo account and instructions are provided to test any usability/functionality/features that you have created.


We're here to help. If you have any questions about the hackathon, post on the discussion forum or email and we'll respond as soon as we can.