Register your connector with the Office 365 Connectors developer dashboard
Building an Office 365 Connector for your application is easy. All you need to do is register your connector in our developer portal, add an integrated configuration experience to your application, and implement your connector. You can make it easy for your users to discover the connector by publishing to our catalog.
Build your own Connector
Registering your Connector
Visit the Connector Developer Portal and login with your Office 365 credentials. If you do not have an Office 365 subscription you can get a one year FREE Office 365 Subscription under the Office 365 Developer Program.
Choose New Connector and fill out the form. Once you choose Save, new options appear on the page.
- The Sideload to Outlook button will temporarily add your connector into the logged on user's Outlook experience. That user will be able to configure the connector either in their inbox or on any group that user is a member of.
- The Publish to Store button will start the publish process, including review by Microsoft for listing in the store.
Adding an integrated configuration experience
For details, see Integrating the configuration experience.
The Integrating the configuration experience document is Microsoft Teams-specific, but the documented methods work the same way in Outlook.
Outlook-specific configuration requirements
If your configuration experience requires authentication, there are additional requirements to enable the authentication flow in Outlook on Windows.
Outlook on Windows passes an additional query parameter to your connectors authentication start page.
Your app must preserve this value and pass it as an additional parameter to the
microsoftTeams.authentication.notifyFailure methods once authentication is complete.
Publish your Connector to the Store
Once you have thoroughly tested your connector and it is ready to be listed in the Office 365 connector catalog, you can use the Publish to Store button to submit it for review. Once reviewed and approved your connector would be added to the connector catalog.
Connector submission checklist
- Ensure that your connector is fully functional and thoroughly tested before submitting it to the Store.
- Test your connector cards in various clients where your users would use it: Outlook on the Web, Outlook 2016 or later, and Outlook Groups mobile apps.
- Ensure that you strictly use Markdown for text decoration and not send HTML in your connector card payload.
- Maintain a balance between adding value and generating too much noise. Ensure that the user is not bogged down with too many notifications.
- Identify the right events to send connector cards for. Ensure that the information you send to the group is valuable to the members of the group.
- When sending reports or summaries, use a digest format and allow the user to choose the time and frequency of the reports.
- When sending connector cards make the best use of Markdown to highlight important parts of the card.
- Make your connector cards actionable by providing relevant actions whenever possible.
- Actions invoked should be really low in failure rate and should have fast response by your endpoint.
- Ensure that you have provisions for the user to pause or remove the configuration.
- Have clear user-facing documentation on the capabilities your connector offers.
- When registering your connector:
- Ensure that the name and logo of your connector does not infringe upon a trademark or copyright of any other product or service.
- Provide a high quality logo of type jpg, jpeg, png or gif that is under 60KB in size.
- Provide a short description of your application (e.g. 'Contoso Help Desk brings companies and customers together').
- Provide a detailed description of your connector (e.g. 'The Contoso Help Desk connector notifies your Office 365 group about activity on your customer's tickets').
- When publishing your connector to Store:
- Make sure to fill out step by step instructions and share test account information to let us test your connector.
Send feedback about: