Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-mail-logging domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the broken-link-checker domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the health-check domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the updraftplus domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-extended-search domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the rocket domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114 Join our Beta Program for the Nextcloud Exchange Connector - NextcloudSkip to main content
Nextcloud users know the importance of integrating different systems and tools to create a seamless workflow. Nextcloud Enterprise allows you to integrate with Microsoft environments for file storage, user directory, Outlook, Sharepoint, Windows Desktop, MS Office online server, and Teams. And now, we are excited to announce a new addition to our lineup: the Nextcloud Exchange Connector.
Developed in partnership with Sendent, the Nextcloud Exchange Connector offers bi-directional syncing with Microsoft Exchange. With this new connector, you can seamlessly sync your contacts and agenda items between Nextcloud Enterprise and Exchange, eliminating the need for double agendas or manual copying and pasting.
Sendent is best-known for their Outlook add-in, which turns email attachments into secure and sharable Nextcloud links, avoiding the sending of risky attachments within organizations. After several requests from clients, Sendent investigated the option to build a connector to link Exchange with Nextcloud. The first iteration of this connector will focus on syncing contacts and agenda items, with more syncing capabilities to be added later.
“At Nextcloud, we believe in the power of integrations to drive and increase productivity on collaboration platforms. Nextcloud Enterprise is designed to integrate well with Microsoft environments. We are excited to partner with Sendent for the development of the Nextcloud Exchange Connector, which will bring new integration capabilities to open up Exchange data to Nextcloud Enterprise.” – Frank Karlitschek, CEO of Nextcloud.
We are thrilled to launch a beta program for the Nextcloud Exchange Connector, and we are inviting users, sysadmins and developers to participate. By joining the beta program, you will have the opportunity to provide feedback and help shape the final version of the connector. Depending on the amount of interest we receive, we may select a specific group of testers to interact with in this beta program.
All signups to the beta program will get early access to the connector. If you simply want to be kept up to date regarding the release of this Nextcloud Exchange Connector, you can also leave us your details so that you will be the first to know.
Don’t miss out on the chance to be one of the first to try out the Nextcloud Exchange Connector.
“When we have welcoming communities of contributors, open source software gets better and more useful to everyone.” Limor Fried, Electrical Engineer, Inventor and Founder of open-source hardware company Adafruit We believe in this ideal and love to work with our community. We are always looking to involve more people in Nextcloud, bringing in their ideas, […]
The Nextcloud Conference is not your average event - it's a community meetup that brings together Nextcloud enthusiasts, contributors, developers, users and industry experts from all over the world.
We save some cookies to count visitors and make the site easier to use. This doesn't leave our server and isn't to track you personally!
See our Privacy Policy for more information. Customize
Statistics cookies collect information anonymously and help us understand how our visitors use our website. We use cloud-hosted Matomo
Matomo
_pk_ses*: Counts the first visit of the user
_pk_id*: Helps not to double count the visits.
mtm_cookie_consent: Remembers that consent for storing and using cookies was given by the user.
_pk_ses*: 30 minutes
_pk_id*: 28 days
mtm_cookie_consent: 30 days