Winter 2024: Deprecation of basic integrations

When a basic integration is deprecated, it is removed from Oomnitza. To avoid any disruptions, you must migrate to the corresponding extended integrations before the Winter 2024 release.

➢ Basic integrations to be deprecated for Winter 2024

For the Winter 2024 release, the following basic integrations will be deprecated:

Basic Asset Integrations	Basic User Integrations
AirWatch	Microsoft Azure
Google Chromebook	BambooHR
Google Workspace mobile devices	Okta
Jamf computers	OneLogin
Jamf mobile devices	Workday
Meraki Systems Manager	Zendesk
SimpleMDM

➢ Switch to an extended integration

To continue syncing your data with Oomnitza, switch to an extended integration.

When you switch from a basic to an extended integration, you can avail of the following benefits:

Extended integrations in Oomnitza offer flexibility in terms of installation options. When creating an extended integration, you have the choice between two installation types: Cloud or Local.

Cloud: With a cloud installation, you create and store your credentials securely in the Oomnitza vault. This approach ensures the safekeeping of your credentials, as they are stored in a protected environment within Oomnitza's infrastructure.

Creating an extended integration in the cloud

Local: With a local installation, your credentials are stored on your own virtual machine or server. This option provides you with the control and ownership of managing your credentials within your own environment.

Creating an extended integration locally

Local installation restrictions

Local installation does not support AWS or OAuth authentication. If the vendor application requires AWS or OAuth authentication, the option to create an extended integration and store your credentials locally is not available

For every basic integration that is in the process of being deprecated, an equivalent extended integration is available. Your historical data will be retained and made available to you in the extended integration.

Basic Integration	Extended Integration counterpart	Is the same API endpoint used?	Installation types
AirWatch	VMware Workspace ONE UEM Asset Load	No, the extended integration for AirWatch has been updated to the new endpoint following its acquisition by VMware, Inc. However, it is important to note that the data returned, specifically MDM devices, remains unchanged.	Local, Cloud
BambooHR	BambooHR User Load	Yes	Local, Cloud
Google Chromebook	Google Workspace Chrome OS Device Asset Load	Yes	Cloud only
Google Workspace mobile devices	Google Workspace Mobile Device Asset Load	Yes	Cloud only
Jamf computers	Jamf Asset and Software Load	Yes	Cloud only
Jamf mobile devices	Jamf Mobile Asset Load	Yes	Cloud only
Meraki Systems Manager	Cisco Meraki Asset Load	Yes	Local, Cloud
Microsoft Azure	Microsoft Azure AD User Load	Yes	Cloud only
Okta	Okta User Load or Okta Deprovisioned User Load (for filtering any user, not just deprovisioned users)	Yes	Local, Cloud
OneLogin	OneLogin User Load	Yes	Local, Cloud
SimpleMDM	SimpleMDM Asset Load	Yes	Local, Cloud
Workday	Workday User Load	Yes	Local, Cloud
Zendesk	Zendesk User Load	Yes, basic and OAuth options are available.	Local, Cloud

➢ Disable your basic integration

If the basic integration is hosted on your own server, make sure that you stop the scheduled execution of the basic integration once your extended integration is up and running. Depending on your operating system, this schedule may have been set up using Task Scheduler on Windows or a cron job on Mac or Linux. Failure to do so may result in continued data synchronization with Oomnitza.

If the basic integration is hosted on Oomnitza's infrastructure, these integrations will be disabled for you.

➢ Support and transition

Your CSM will contact you before the Winter '24 release to assist with the transition to the corresponding extended integration. For additional information, please reach out to your CSM or contact support.