Connect Microsoft Dynamics 365 CRM and Okta 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 Microsoft Dynamics 365 CRM with Okta - 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 Account" from Microsoft Dynamics 365 CRM.
Add your action
An action happens after the trigger—such as "Activate User" in Okta.
You’re connected!
Zapier seamlessly connects Microsoft Dynamics 365 CRM and Okta, 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 Account
Triggers when a new account is created.
Try ItTriggerPolling - New Contact
Triggers when a new contact is created.
Try ItTriggerPolling - Custom EntityRequired
Try ItTriggerPolling
- New Case/Incident
Triggers when a new case/incident is created.
Try ItTriggerPolling - New Invoice
Triggers when a new invoice is created.
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 Dynamics 365 CRM on the Zapier blog
Learn how to automate Okta on the Zapier blog
Frequently Asked Questions about Microsoft Dynamics 365 CRM + Okta integrations
New to automation with Zapier? You're not alone. Here are some answers to common questions about how Zapier works with Microsoft Dynamics 365 CRM and Okta
What are the key prerequisites for integrating Microsoft Dynamics 365 CRM with Okta?
Before integrating Microsoft Dynamics 365 CRM with Okta, ensure you have admin access to both platforms. You will need to configure API access and permissions within Dynamics 365, as well as set up the appropriate authentication and provisioning settings in Okta.
How does single sign-on (SSO) work between Microsoft Dynamics 365 CRM and Okta?
Single sign-on (SSO) allows users to log in once through Okta and gain access to Dynamics 365 CRM without needing separate credentials. We use SAML or OpenID Connect protocols to facilitate secure authentication tokens that log users into Dynamics automatically.
Can we automate user provisioning from Okta to Microsoft Dynamics 365 CRM?
Yes, our integration supports user provisioning. When a new user is added in Okta, it triggers the creation of that user within Microsoft Dynamics 365 CRM. You can map attributes between the two systems to ensure accurate data transfer during provisioning.
Is it possible to sync group memberships from Okta into Dynamics 365 CRM?
Syncing group memberships is supported. Through our integration, changes in group assignments in Okta can automatically update corresponding roles or teams in Dynamics 365 CRM using predefined triggers and mapping configurations.
How is deactivation of users managed in this integration?
User deactivation is handled seamlessly—when a user account is deactivated or suspended in Okta, it triggers an action that automatically disables their corresponding account or reduces their permissions within Microsoft Dynamics 365 CRM.
Are there specific actions that can be triggered within Microsoft Dynamics from Okta workflows?
Yes, you can trigger various actions such as updating user information, adjusting security roles, or initiating custom workflows directly within Microsoft Dynamics based on events occurring in Okta using our advanced workflow automation features.
What kind of support do we offer for troubleshooting issues during integration?
We provide extensive documentation and support resources for troubleshooting. Our team is available for assistance with common issues such as configuration errors, API connectivity problems, and understanding alert/logging outputs during the integration process.