- #Import calendar csv into outlook 365 how to#
- #Import calendar csv into outlook 365 install#
- #Import calendar csv into outlook 365 update#
- #Import calendar csv into outlook 365 code#
Additionally, there’s a variety of options to specify the EWS Url manually, switching to the Exchange 2007 version of the API etc.
If you’re not logged on as the user you want to use for the import, you can specify a username and password. This is used when impersonating, and for Autodiscover. The format of the file is intentionally the same as Outlook will export in, mainly because a lot of apps already export in the format (Gmail does, for example) so you should find it easy to get test data, but if you haven’t I’ve included a sample file to get you started.Īlong with the data, you also need, at a minimum, the mailbox email address to import to. You should be good to go!įor each mailbox you want to import contacts from you need a separate CSV file. So, you’ve got impersonation setup if needed, got the EWS DLL on your machine. Using the script Import-MailboxContacts.ps1 Once downloaded and installed, you should be good to go with script.
#Import calendar csv into outlook 365 install#
The easiest way to get up and running is to download the API (choosing the right version for your platform), and install it to it’s default location.ĭownload the EWS Managed API v1.2 from the Microsoft site Next, whatever environment you are in, you need a copy of the DLL file that provides the bits and pieces that make this all work. Installing the Exchange Web Services Managed API
#Import calendar csv into outlook 365 how to#
Full details of how to setup impersonal are on the Microsoft site, but if you just want to get it setup for a single admin/service account, org-wide, use the following command substituing serviceaccount for your service account: In Exchange 2010, setup of Exchange impersonation is managed via RBAC. If you’re planning on doing a mass-import of contacts, or don’t know the user’s password you’re importing, then setup of EWS impersonation is the step you need to take to allow a trusted account to switch to the user you want to import.
#Import calendar csv into outlook 365 update#
Most actions that can be performed in Outlook can be performed via EWS – so much so, in fact, that Apple’s Mail.app in Snow Leopard and the latest update for Entourage 2008 use EWS as the backend for the mail clients themselves. Setup of Exchange Web Services ImpersonationĮxchange Web Services is the programmatic interface to each user’s Exchange mailbox.
Don’t worry though! It’s nothing too onerous – all is needed to get going is two things: Getting startedīefore you can run this script, there are a few things you need to set up first.
#Import calendar csv into outlook 365 code#
The reason that Powershell is the right language for code like this is that it’s fairly easy for the enterprising administrator to modify to their needs. What I’ve heard is it would be useful to have some Powershell code that out-of-the box can import contacts into any Exchange mailbox. While this isn’t the actual code I used (I wrote my original code in C#), I’ve re-visited what I’ve done and listened to what others say they need.
While Microsoft provide IMAP migration tools to move mail to Outlook Live (which I was lucky enough to beta test before it was widely available), no tools are provided to move other data such as contacts and calendars.
When performing migrations between different systems, there’s always the case where the tools available don’t do the job out of the box – and although IMAP migration tools for Exchange and Outlook Live can be great for moving mail, there isn’t a decent free solution for importing contacts.įor a recent migration from a Unix system (Dovecot + SquirrelMail) to Outlook Live, I came across this very scenario.