in Office 365

Making your Office 365 App Available to Multiple Organizations

When building your web application or Windows Store app accessing Office 365 data, you might be working with just your Office 365 tenant. However, when you publish your app, you may want to make your application available to all Office 365 users (depending on your scenarios). This means, users not only from your Office 365 tenant, but also from other tenants will be able to log in and use your application.

Publishing your Office 365 App

First, you will need to know how to publish your Office 365 app to production. Tobias Zimmergren has done a great job outlining the steps.

App Properties

In the Office 365 API tooling, you will notice there is an option for App Properties

Office 365 API App Properties

Office 365 API App Properties

App Properties, as its name suggests, is where you can edit some of the properties available for your Office 365 app.

Today, you can edit the following:

– Name of your application

– Multi-tenant configuration

Office 365  App Properties

Office 365 App Properties

Making your App Available to Multiple Organizations

If you want your application that is consuming Office 365 data using the Office 365 APIs to be accessed not only by your organization but also from other external organizations, then you will need to set this setting to Multiple Organizations.

Setting this to Single Organization will only allow your single-organization users to access the Office 365 data.

NOTE: An Office 365 app is nothing but an Azure Active Directory application and thus this setting  applies to the Azure Active Directory Application. Hence, this will be applicable to any other (non Office 365) resources that your app is consuming.

Another thing to note is that this setting is only available to web applications and not for native client applications such as Windows Store apps. For native client applications, this is set to Multiple by default.

I would highly recommend reading the documentation before you publish your application to make the right decision.

How does this work?

You have now configured your app to be available to multiple organizations and you may ask what happens when external users sign in.

When external users sign in, they will see the consent dialog and have to grant access to the application to access their Office 365 data.

External Users Consent Dialog

External Users Consent Dialog


With the Office 365 API tool, you can easily configure for your application consuming Office 365 API to be available to not only your organization but also to external users who may belong to multiple organizations.

Write a Comment


Time limit is exhausted. Please reload the CAPTCHA.

  1. Maybe you can answer this. I’m a developer with an azure tenant that I pay out of my own pocket.
    I want to develop SharePoint apps that can be used by multiple organizations but I don’t have a SharePoint subscription linked to my azure tenant. My SharePoint sub is linked to my msdn subscription azure subscription. Is there someway to deploy/host a multitenant azure ad app in my personal Azure subscription that doesn’t subscribe to the resources (SharePoint) the app wants access to?

  2. Can all flavors of Office 365 access a third-party multi-tenant app, or is that feature only available for certain kinds of accounts?