Cloudiway’s Free/busy calendar coexistence solution is ideal for company mergers, or for companies that require a long-term solution to interoperability. It’s simple to set up and maintain. Cloudiway provides a cloud-based application that manages coexistence without requiring any software installation or overhead.
Calendar coexistence manages cross-platform communication with no impact on the end-user. It provides a seamless connection between vastly different remote systems, such as G Suite, Office 365, and Exchange.
For example, a G Suite user can check the free/busy time of an Office 365 user using Google’s standard calendar interface. Similarly, an Office 365 user on one domain can check the free/busy time of an Office 365 or G Suite user on an entirely different domain.
To achieve this, each remote system needs to be configured to communicate with Cloudiway, including its own ‘connector’ on the Cloudiway platform. The connector allows queries to each system’s free/busy data and a response, which Cloudiway then returns to the enquirer.
For example, firstname.lastname@example.org (using G Suite) wants to know if email@example.com (using Office 365) is available for a meeting. Bob checks if Chloe is free by creating a meeting request.
Behind the scenes, an availability query is sent to Cloudiway, which first checks for a connector for redfitness.com, then queries it for Chloe’s availability. Cloudiway sends the query results back to Bob so that he can see if Chloe is available at the specified time.
See the next page for more details.
Using Bob and Chloe’s meeting as an example, Bob opens his Google calendar and invites Chloe to a meeting, then clicks on the Find a Time tab to see her free/busy time.
You can also use coexistence during mailbox migrations, which is covered in more detail elsewhere. Basically, during migration with coexistence, end users can continue working without interruption. When a mailbox is migrated, address books are synchronized, the mail is rerouted, and free/busy time is available at both the source of the migration and at the target.
Calendar free/busy coexistence can be implemented between two or more remote systems. Currently, the following systems are supported, including any combination and number of these:
If you are using Exchange On-Premises 2010 or any other system, please get in touch with our technical consultants at firstname.lastname@example.org to discuss how coexistence can be implemented with your combination of remote systems.
This guide is aimed at system administrators who are capable of connecting to remote systems such as Exchange Online and Office 365 Admin Panel. Coexistence is a detailed setup that requires a high level of competence and experience with PowerShell.
Although we provide support for our products, we do not provide support for third-party products such as PowerShell or server administration of Google or Exchange.
If you are concerned you might have any difficulty completing these steps, please consider a solution with our consulting team, contactable via email@example.com. This will ensure a fast, cost-effective, and stress-free implementation.
This guide covers three different types of connectors for enterprise coexistence: Office 365, Exchange On-Premises, and G Suite. For clarity, this guide uses a different business name for each:
The screen dumps used in this guide reflect these business names to provide typical examples of data to enter into each field.
In addition, this guide covers calendar free/busy between the three separate systems. You can skip any sections for systems that won’t be used as part of your cross-platform setup.
We take your privacy and security seriously at Cloudiway, and we have invested significant effort into making our platform and your data secure. Cloudiway provides a cloud-based application hosted on Windows Azure. It means that the software and data are centrally hosted and accessed by clients using a web browser and internet connection. In addition, Cloudiway’s SaaS benefits from Windows Azure’s certifications, ensuring the security of the infrastructure, network and physical security layers of the Cloudiway cloud.
For total assurance, Cloudiway provides auditing tools, secure, authenticated data connections, and a logging system. More specifically:
There are four simple steps to configuring a remote system to coexist with another remote system:
Each Cloudiway connector requires a domain name as well as security credentials to allow two-way communication. G Suite also requires Service Account details (email and private key) before the connector can be saved.
You can set up any remote system to coexist at any time. However, you must adhere to the order outlined in each section below, to avoid coexistence being activated before all the required steps have been completed.
NOTE: If you configure your remote systems prior to contacting Cloudiway, you risk being blacklisted by Google and/or Office 365.
Before you start, ensure you have the details outlined in the following table.
|Cloudiway login||Stores details and provides communication between the systems you already use.||https://portal.cloudiway.com|
|Knowledgebase access||Our extensive knowledgebase is always accessible, with videos, troubleshooting tools, samples and more.||https://kb.cloudiway.com|
|Cloudiway Tokens (name and private access token)||These details are the unique identifiers associated with each of your systems.||https://portal.cloudiway.com/tokens (or go to Account Settings from your username when you’re logged into Cloudiway).|
|Your Cloudiway URL||Cloudiway will assign a URL to your profile for coexistence (eg, coexistence.cloudiway.com).||Usually, this is coexistence.cloudiway.com, but for larger projects, you will be given a dedicated environment. Please contact Cloudiway for further details.|
There are three simple steps to implementing coexistence with Google:
The steps should be completed in that order to ensure coexistence only begins when you’re ready. Each step is explained thoroughly in the sections below.
|G Suite API console||Required to enable APIs and to download the G Suite private key. This can be accessed via your Google Admin account.||https://console.developers.google.com|
|Google Admin console||The Admin console is where administrators manage Google services for people in an organization.||https://admin.google.com|
|Standard Google user account||A standard G Suite user mailbox with no specific permissions.||Every free/busy lookup will be performed with the identity of this account. We recommend using firstname.lastname@example.org.|
|Office 365 login with admin access||Required later on to ensure an admin login has the Address Lists management role||Office 365 cloud login|
|Windows PowerShell||Required to access Exchange remotely to set up free/busy requests for resources (users and rooms).||https://technet.microsoft.com/en-us/library/dn975125.aspx|
|Office 36 standard user account||A standard Office 365 user created in the cloud with an Exchange license and no specific permissions.||Every free/busy lookup will be performed with the identity of this account. We recommend using email@example.com.|
Cloudiway is currently configured to work with Exchange On-Premises 2013 and later only. If you’re using Exchange 2010, please contact us. Our technical consultants will be able to discuss your plan and advise you on additional setup requirements that we can undertake on your behalf.
|Exchange standard user account||A standard Exchange user with no specific permissions.||Every free/busy lookup will be performed with the identity of this account. We recommend using firstname.lastname@example.org.|
|Port requirements||The Cloudiway platform needs to connect to Exchange On-Premises securely.||Use SSL port 443.|
You can use the Google Admin console to manage the service and its API calls. The following steps show you how to grant access permissions for the service account provided by Cloudiway.
Cloudiway owns a service account that reduces the complexity of having to create your own service account. All you have to do is grant the privileges to access your data.
For Cloudiway to successfully provide coexistence between two remote systems, it needs information from both in the form of the Cloudiway connector. You will need to set up a connector for each domain intended to coexist.
Follow the steps below to configure the G Suite (Cloudiway will route all free/busy requests through a single user on your system. We recommend you create a new user specifically for this (for example, email@example.com). You will need to add this email address in the steps below.), Office 365 or Exchange On-Premises side of communication with Cloudiway (we will use the Office 365 or Exchange On-Premises standard user account mentioned in the table above).
Before testing your connectors, you need to add some users. This is a simple task involving a single user associated with each of your connectors (so, a minimum of two individual users). Make sure you have the login credentials for each of your test users.
Please note that any further configuration steps you take after creating your test users may cause you to be blacklisted by Google or Office 365, so please follow the steps below and then contact Cloudiway to confirm you’re ready to test coexistence. Your Cloudiway contact will be in touch after checking over your configuration and will ask you to complete the coexistence testing prior to final activation.
Now that you’ve set up your connectors and test users, you should contact Cloudiway to activate your account − and your coexistence. Contact firstname.lastname@example.org to request activation.
Cloudiway will come back to you with information relating to the Cloudiway server URL that you will need to use in the following steps.
Once you’ve heard back from us, we’ll work with you to test your connectors, then activate coexistence. Please note that further configuration at this stage may lead to you being blacklisted on Google and, or Office 365.
As soon as the steps below are performed, Cloudiway can complete the configuration so that communication can begin.
For G Suite coexistence to work, you need to enable the URI request in Cloudiway. You will also need the Cloudiway URL that has been assigned to you.
The configuration of free/busy requests requires an available address space. The ‘add availability address space’ command instructs Office 365 to forward free/busy requests to the Cloudiway platform.
In the steps below, we will create an available address space. In order to create an availability address space, an availability config must exist. The Cloudiway platform doesn’t use this config in any way, but this is required to run the commands.
To connect to your Exchange Online server, you will need to have a basic working knowledge of Windows PowerShell.
New-AvailabilityConfig -OrgWideAccount limitedUser@company.com
(where limitedUser@company.com is whatever email address on your Exchange server that you want; the Cloudiway platform won’t use this account) The script will output something similar to the text below:
$adminCredsId = "\TokenKey" $adminCredsPassword = "SecretToken" $securePassword = ConvertTo-SecureString $adminCredsPassword -AsPlainText -Force $adminCreds = New-Object System.Management.Automation.PSCredential($adminCredsId,$securePassword) Add-AvailabilityAddressSpace ` -AccessMethod OrgWideFB ` -ForestName domainname.com ` -Credentials $adminCreds ` -TargetAutodiscoverEpr "https://XXX.cloudiway.com/autodiscover.xml"
The steps below work only for Exchange On-Premises 2013 and later. If you have Exchange OnPremises 2010, please get in touch to discuss calendar free/busy coexistence implementation.
$adminCredsId = "\TokenKey" $adminCredsPassword = "TokenSecret" $securePassword = ConvertTo-SecureString $adminCredsPassword -AsPlainText -Force $adminCreds = New-Object System.Management.Automation.PSCredential($adminCredsId,$securePassword) Add-AvailabilityAddressSpace ` -AccessMethod OrgWideFB ` -ForestName domainname.com ` -Credentials $adminCreds ` -TargetAutodiscoverEpr "https://XXX.cloudiway.com/autodiscover.xml"
If you receive any error messages, check TechNet online (eg: https://technet.microsoft.com/enus/library/bb124122(v=exchg.160).aspx) for more details. If you still need further help, please consider a solution with our consulting team, contactable via email@example.com.
NOTE: If you use a proxy server with Exchange On-Premises 2010 or 2013, please get in touch with our consulting team to check and resolve any conflicts.
Office 365 and Exchange can only query the free/busy time of objects that already exist in the global address book. In order to test the free/busy time of the remote system of Office/Exchange, you must:
The test contact must match the test user that you created for the other connector in section 4.9. Make sure you use the right test user (ie, the one that doesn’t already exist in your global address list).
$UserCredential = Get-Credential $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection Import-PSSession $Session
At this point, your system configuration is complete and you’re ready to test coexistence with your test users.
To test, log in to each of your source systems with your test user credentials (for each test user you set up in section 4.7 and open each test user’s calendar. Verify that each test user can see the other’s free/busy time. You should be able to see free/busy time in both directions.
Once you’re satisfied that coexistence is working as expected, you can import your remaining users and go live.
The easiest way to import all your users is via CSV upload. The Cloudiway platform provides an interface for CSV uploads. The CSV file needs just two columns:
where SourceName matches the name of the corresponding Cloudiway connector for each user.
The Cloudiway platform will process your CSV file. You can check and activate the status of each connector associated with a different user.
Remember, Office 365 and Exchange can only query free/busy time of objects that already exist in its global address book.
Cloudiway provides an extensive knowledge base with many resources, including common error messages, video guides, and downloads.
The knowledge base also contains information on how you can ask for further support, should you require it. Please visit the entire knowledgebase here (where you can search for keywords or read through topics): https://kb.cloudiway.com/