Connect Jenkins and Microsoft Office 365 to unlock the power of automation
- No credit card required
- Free forever for core features
- 14-day trial for premium features and apps
How Zapier works
Zapier makes it easy to integrate Jenkins with Microsoft Office 365 - no code necessary. See how you can get setup in minutes.
Choose a trigger
A trigger is the event that starts your Zap—like a "New Job Status Notification" from Jenkins.
Add your action
An action happens after the trigger—such as "Create Event" in Microsoft Office 365.
You’re connected!
Zapier seamlessly connects Jenkins and Microsoft Office 365, automating your workflow.
Supported triggers and actions
Zapier helps you create workflows that connect your apps to automate repetitive tasks. A trigger is an event that starts a workflow, and an action is an event a Zap performs.
- New Job Status Notification
Catches job status notifications sent via the Notficiation Plugin
Try ItTriggerInstant - Parent FolderRequired
- Child Folder
Try ItTriggerPolling- Contact Folder
Try ItTriggerPolling- Parent Folder
- Child Folder
- Search termsRequired
- Note
Try ItTriggerPolling
- Calendar
- Time BeforeRequired
- Time Before (Unit)Required
Try ItTriggerPolling- Calendar
Try ItTriggerPolling- Shared Inbox
Try ItTriggerPolling- New Flagged Email
Triggers when a new email is flagged.
Try ItTriggerPolling
Zapier is the automation platform of choice for 87% of Forbes Cloud 100 companies in 2023




93%
Customers who say using Zapier has made them better at their job
25m
Customers have created over 25 million Zaps on the platform
6 mins
The average user takes less than 6 minutes to set up a Zap
Learn how to automate Microsoft Office 365 on the Zapier blog
Frequently Asked Questions about Jenkins + Microsoft Office 365 integrations
New to automation with Zapier? You're not alone. Here are some answers to common questions about how Zapier works with Jenkins and Microsoft Office 365
How can I integrate Jenkins with Microsoft Office 365 for automated notifications?
You can set up a Zap where Jenkins builds trigger an action in Office 365, such as sending an email or creating a calendar event. This helps ensure that your team stays informed about the build status without manually checking Jenkins.
Can I create calendar events in Outlook from Jenkins build completions?
Yes, by using our integration, you can set a trigger when a Jenkins build completes and automatically create an event in your Office 365 Outlook calendar. This is useful for scheduling follow-up tasks or reviews.
Is it possible to trigger an automatic email alert in Office 365 when a Jenkins job fails?
Certainly! Our integration allows you to configure a trigger for failed jobs in Jenkins, which can then automate the sending of an alert email via Office 365 to specified recipients.
How do we ensure security when integrating Jenkins with Office 365?
We prioritize security by supporting OAuth for authentication with Microsoft services, ensuring that your credentials are always protected. Moreover, you can customize permissions to control access precisely between the two applications.
What steps are involved in setting up the integration between Jenkins and Microsoft Office 365?
To set up the integration, first connect both Jenkins and Office 365 accounts through our platform. Then define triggers like 'new build completed' or 'job failed' and link them to actions such as sending emails or creating tasks in Office 365.
Can multiple actions be triggered from a single event in Jenkins using this integration?
Yes, our platform supports triggering multiple actions within Office 365 from one event in Jenkins. For example, upon successful build completion, you could send out notification emails and also update a task list simultaneously.
Does the integration support actions based on scheduled builds in Jenkins?
Indeed, you can configure triggers based on scheduled builds so that certain actions like reminders via email or task creation occur automatically at predefined times aligned with your continuous integration cycle.