Connect Freshservice 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 Freshservice 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 Ticket" from Freshservice.
Add your action
An action happens after the trigger—such as "Create Event" in Microsoft Office 365.
You’re connected!
Zapier seamlessly connects Freshservice 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 Ticket
Triggers when there is a new ticket is created in Freshservice.
Try ItTriggerInstant - Updated Ticket
Triggers when a Ticket is updated.
Try ItTriggerInstant - Ticket NoRequired
- NotesRequired
- PrivateRequired
ActionWrite- First NameRequired
- Last Name
- Job Title
- Primary EmailRequired
- Mobile Phone Number
- Work Phone Number
- Address
- Background Information
ActionWrite
- New User
Triggers when a new User is created.
Try ItTriggerInstant - Update User
Triggers when a user is updated.
Try ItTriggerInstant - SubjectRequired
- DescriptionRequired
- Ticket StatusRequired
- Type
- EmailRequired
- CC Emails
- Category
- Priority
- Urgency
- Impact
- Department
- Group
- Source
ActionWrite- Ticket
- Approval TypeRequired
- ApproverRequired
ActionWrite
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 Freshservice + 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 Freshservice and Microsoft Office 365
What is required to connect Freshservice with Microsoft Office 365?
To connect Freshservice with Microsoft Office 365, you need to have admin access to both platforms. Ensure that all permissions are properly set up in the Office 365 admin center and that API access is enabled in Freshservice.
How can I set up automated ticket creation using triggers from Microsoft Office 365 emails?
You can configure triggers in Office 365, such as receiving an email from a specific sender or with a particular subject line, to automatically create tickets in Freshservice. This involves setting rules within your email flow on Office 365 and using Freshservice's automation tools.
Can events on my Office 365 calendar impact Freshservice tasks?
Yes, you can configure actions such as creating a task or triggering alerts in Freshservice when specific events occur on your Office 365 calendar. This synchronization is helpful for aligning schedules and ensuring team awareness of important dates.
Is it possible to integrate contact details between Microsoft Office 365 and Freshservice?
Integrating contact details involves syncing user information between both platforms. Any updates made in the contacts on one platform can be triggered to reflect in the other, keeping records consistent across systems.
How does authentication work when integrating Freshservice with Office 365?
Authentication for integration typically involves OAuth or service accounts where tokens are exchanged securely. We ensure that this process complies with security standards to protect your data during integration.
Can you automate status updates in Freshservice based on Outlook mail actions?
Yes, by setting up certain triggers like flagging an email or moving it to a specific folder in Outlook, automatic updates can be reflected within your ticketing dashboard on Freshservice.
Are there limitations I should be aware of when integrating these two systems?
While many features can be integrated smoothly, some limitations might exist based on API capabilities and permissions set within each system. It's important to consult the documentation for both platforms during setup.