Friday, 8 November 2013

Azure IRM templates in Outlook appear in Vietnamese although the the localisation setting in Windows is "English – United Kingdom"

Problem: Azure IRM templates in Outlook appear in Vietnamese although the the localisation setting in Windows is "English – United Kingdom"

Special thanks to Phil Hodson for identifying the route cause of the issue and resolving it. 

The default “Confidential” and “Confidential – View Only“ templates provided by Azure IRM contain translations for a number of regional LCIDs.

In our case, we set the localisation settings to “English – United Kingdom” in Windows (LCID: 2057)

There is no translation in the templates for LCID 2057 - so Office 2013 simply defaults to the first one listed in the template; LCID 1066 (Vietnamese):

LCID 1066:NAME Company Name - Thông tin mật:DESCRIPTION Nội dung này là thông tin độc quyền chỉ dành cho người dùng nội bộ. Nội dung này có thể được sửa đổi nhưng không thể được sao chép và in ra.;

There are two possible solutions to this issue:

1) Preferred: Add the 2057 Locale (and any other missing Locales) to the templates with appropriate translations

2) Alternative: Set the 1033 (English – US) locale to be the first in the list, so that the default Language seen in Office is English.

We have tested both solutions by editing the locally cached templates under “%LOCALAPPDATA%\Microsoft\MSIPC\Templates” and have confirmed they work.

The templates currently contain the following LCIDs (in order).

Anyone using a Locale that isn’t on the list will see Vietnamese

Locale ▾               LCID Decimal
Vietnamese 1066
Lithuanian 1063
Latvian 1062
Estonian 1061
Slovenian 1060
Ukrainian 1058
Indonesian 1057
Turkish 1055
Thai 1054
Swedish - Sweden 1053
Slovak 1051
Croatian 1050
Russian 1049
Romanian - Romania 1048
Portuguese - Brazil 1046
Polish 1045
Norwegian - Bokml 1044
Dutch - Netherlands 1043
Korean 1042
Japanese 1041
Italian - Italy 1040
Hungarian 1038
Hebrew 1037
French - France 1036
English - United States 1033
Greek 1032
German - Germany 1031
Danish 1030
Czech 1029
Chinese - Taiwan 1028
Bulgarian 1026
Arabic - Saudi Arabia 1025
Chinese - China 2052

Thursday, 7 November 2013

Real-time co-authoring is now available in Office Web Apps

Real-time presence helps you see where your co-authors are working in the document so that you don't create conflicts as you edit. Additionally, the new ability to see changes to text and formatting as they happen will help you and your co-authors stay on the same page as your ideas develop and evolve.

And because Office Web Apps now save as you go, your team's edits are included and seen as they happen. 

Read the full announcement here:

Wednesday, 4 September 2013

SkyDrive Pro storage space in Office 365 is now 25 GB (up from 7 GB)

The default SkyDrive Pro storage space in Office 365 is now 25 GB-for both new and existing customers.

Each user in SharePoint Online for Office 365 gets an individual storage allocation of 25 GB for personal site content. Personal sites include the user’s SkyDrive Pro library, a Recycle Bin, and personal newsfeed information.

All SharePoint Online in Office 365 plans include the same storage allocation for individual personal sites. This storage allocation is separate from the tenant allocation.

In addition, SharePoint Online admins can now increase SkyDrive Pro storage space for those individuals that need and want more than the default 25 GB of storage. You can select increases in increments, up to 50 GB or 100 GB (the current SkyDrive Pro limit), and you can adjust the storage for up to 25 users at once. The storage you allocate will come from your tenant's overall pool of storage and you have clear visibility of how much total available tenant storage your company has to allocate to your users' SkyDrive Pro.

Tuesday, 3 September 2013

Exchange Online mailbox sizes are doubling to 50GB

The size of user mailboxes in all Exchange Online and Office 365 service plans is doubling. Beginning on 29th of August, the current 25 GB of mailbox storage is increasing to 50 GB. With this increase even the most active email users don't have to worry about mailbox size limitations. 

There's no price increase associated with this change.

You don't need to do anything to take advantage of this new mailbox size. Your mailbox size will automatically be increased. The increase starts rolling out to customers from end of August and continues through November.

Thursday, 29 August 2013

Windows PowerShell cmdlets for Windows Azure AD Rights Management service

Windows PowerShell cmdlets for Windows Azure AD Rights Management service
Opens a connection to the Windows Azure AD Rights Management service.
Closes a connection to the Windows Azure AD Rights Management service.
Disables the Windows Azure AD Rights Management service.
Enables the Windows Azure AD Rights Management service.
Returns the current configuration of Windows Azure AD Rights Management, including information on all features states, and configuration data for rights management.
Adds a member user or group to the list of those that are able to administer Windows Azure AD Rights Management.
Lists the member users or groups that can administer Windows Azure AD Rights Management.
Removes a member user or group from the list of those that are able to administer Windows Azure AD Rights Management.
Generates a log of administrative commands performed against the Windows Azure AD Rights Management service.
Enables the Windows Azure AD Rights Management super user feature to provide all rights to access protected content for specified users.
Assigns super user rights to a user by e-mail address within your organization.
Lists users within your organization who have super user privileges.
Removes super user rights from a user by e-mail address within your organization.
Returns the currently set migration URL for Windows Azure AD Rights Management installations that have migrated to AD RMS.
Set- AadrmMigrationUrl
Sets the migration URL for use in migrating away from Windows Azure AD Rights Management.

Friday, 9 August 2013

Office 365 will no longer support Internet Explorer 8 after 8 April 2014

Office 365 will no longer support Internet Explorer 8 after 8 April 2014.

For the best, richest experience with Office 365, we strongly recommend that you upgrade to the latest version of Internet Explorer. Internet Explorer 10 is available now, and Internet Explorer 11 is coming soon. Modern versions of Internet Explorer offer faster web browsing, integrated spell-checking, improved security, and more.

Internet Explorer 8 users will not be blocked from connecting to Office 365 after 8 April 2014; however, Internet Explorer 8 users should expect slower performance with Office 365’s Outlook Web App and other Office Web Apps.

If you experience a technical problem connecting to Office 365 from Internet Explorer 8 after 8 April 2014, Microsoft Customer Support and Service may need you to reproduce the problem on a supported browser.

End of support for Windows XP

Microsoft will end all support for Windows XP on 8 April 2014—please upgrade all Windows XP workstations to Windows 8 or Windows 7 prior to this date.

While Office 365 will not block connections from fully patched Windows XP computers after 8 April 2014, connectivity to the service will be at risk. Windows XP workstations that have not deployed all service packs and automatic updates run an even higher risk of Office 365 connectivity issues after support for Windows XP ends.

If you experience a technical problem connecting to Office 365 from a Windows XP machine after 8 April 2014, Microsoft Customer Support and Service will need you to reproduce the problem on a supported operating system.

Tuesday, 6 August 2013

Exchange 2013 Deployment Assistant has been updated

The following two scenarios are now included in the tool:
  • Upgrading from a mixed Exchange 2007 and Exchange 2010 organization to Exchange 2013
  • Configuring an Exchange 2013-based hybrid deployment for Exchange 2010 organizations

To read the full announcement visit:

You can find the tool here:

Monday, 8 July 2013

Enable multi-factor authentication for a user in Office 365

Use the following procedure to enable multi-factor authentication for a user account. Please note that this feature is in preview.

1. Login to Windows Azure Management Portal.
2. Click Active Directory, and then click Directory.

3. Click on your Windows Azure AD tenant. 

4. Click on the Users tab.

5. On the Users page, search for the user you want to enable 2FA for and click on it.

6. Under role, select the Require Multi-factor Authentication check box.

When you select this option, the user must use a phone or another device and their password each time they need to sign in.

Please be aware that once multi-factor authentication is enabled on a user account, that user must complete the auto-enrollment when signing in. This will occur the first time the user signs in after the account has been enabled for multi-factor authentication. Until the user has done this, multi-factor authentication will not be enabled on the account.

Friday, 5 July 2013

Powershell command to get a list of Office 365 users with their assigned licenses

In order to get a list of all the users in your Office 365 tenant with the licenses that are assigned to them, you can run the following command. Change "c:\users.csv" to the location that you want to save the file.

Get-MsolUser -All | ft displayname , Licenses | Out-File c:\users.csv

This report will have both Display Name and License type in same column. If you need to split them into two columns, you can use the "Text to Columns" feature in Excel under the DATA tab to do this. I managed to split them by selecting Other under Delimiters and split where "{" is.

This is because licenses start with "{" and end with "}" (for example if the user's assigned license is E3, it would show as {mytenant:ENTERPRISEPACK}).

Force a full password synchronization using the new DirSync tool with password sync feature

In order to force a full password sync in the new Windows Azure Active Directory Synchronization tool for Office 365, you need to do the following:

  1. Open Registry Editor
  2. Browse to HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft > MSOLCoExistence > PasswordSync.
  3. Change the "FullSyncRequired" registery key value to 1.
  4. Go to Services
  5. Restart the "Forefront Identity Manager Synchronization Service" - this will also restart the Windows Azure Active Directory Sync Service.
  6. Once done, you will notice logs with Event IDs 656 which are the "Password Change Request" events  and 657 which are the "Password Change Result" events.

Monday, 3 June 2013

Password sync is now available for Office 365 (DirSync with password sync feature)

By deploying password sync in your environment, you enable your users to use the same password they are using to logon to your on-premises Active Directory to logon to Windows Azure Active Directory.

The latest version of the Directory Sync tool (version 1.0.6385.0012) can be downloaded from the Office 365, InTune and Azure UX Portals.

What is Password Sync

Password Sync is a feature of the Windows Azure Active Directory Sync tool that synchronizes user passwords from your on-premises Active Directory to Windows Azure Active Directory (“Azure AD”). This feature enables your users to log into their Azure Active Directory services (such as Office 365, InTune, CRM Online, etc.) using the same password as they use to log into your on-premises network. It is important to note that this feature does not provide a Single Sign-On (SSO) solution because there is no token sharing / exchange in the Password Sync based process.

How Password Sync Works

Password Sync is an extension to the directory synchronization feature implemented by the Directory Sync tool. As a consequence of this, this feature requires directory synchronization between your on-premise and your Windows Azure Active Directory to be configured.

The Active Directory Domain Service stores passwords in form of a hash value representation of the actual user password. The Password hash cannot be used to login to your on-premises network. It is also designed so that it cannot be reversed in order to gain access to the user’s plaintext password. To synchronize a password, the Directory Sync tool extracts the user password hash from the on-premises Active Directory. Additional security processing is applied to the password hash before it is synchronized to the Azure Active Directory Authentication service. The actual data flow of the password synchronization process is similar to the synchronization of user data such as DisplayName or Email Addresses.

Passwords are synchronized more frequently than the standard Directory Sync window for other attributes. Passwords are synchronized on a per-user basis and are generally synchronized in chronological order. When a user’s password is synchronized from the on-premises AD to the cloud, the existing cloud password will be overwritten.

When you first enable the Password Sync feature in your DirSync tool, it will perform an initial synchronization of the passwords of all in-scope users from your on-premises Active Directory to Azure Active Directory. You cannot explicitly define the set of users that will have their passwords synchronized to the cloud. Subsequently, when an on-premises user changes their password, the Password Sync feature will detect and synchronize the changed password, most often in a matter of minutes. The Password Sync feature will automatically retry failed user password syncs. If an error occurs during an attempt to synchronize a password the error is logged in your event viewer.

The synchronization of a password has no impact on currently logged on users. If a user that is logged into a cloud service also changes their on-premise password, the cloud service session will continue uninterrupted. However, as soon as the cloud service attempts requires the user to re-authenticate, the new password needs to be provided. At this point, the user is required to provide the new password – the password that has been recently synchronized from the on-premise Active Directory to the cloud.


Friday, 31 May 2013

Get total number of Office 365 users using PowerShell

Here is a quick PowerShell command to get a total number of Office 365 users:

$allUsers = Get-MsolUser -All

Friday, 24 May 2013

How to correctly apply Directory Synchronization (DirSync) filters plus some useful observations

When applying Connector Filters to Source AD Management Agent on Directory Synchronization tool (DirSync) for Office 365, although it looks like you can put few conditions in one filter, however in practice it didn't work for me.

Here is the attempt on putting multiple conditions in one filter to apply on the user object, which didn't work:

When you apply new filters, the incremental sync normally doesn't pick up the changes. In order to force the new filters, you need to run a "Full Import Full Sync" on the source AD.

Here are the same conditions, but each created as a separate filter. This is the working configuration:

Once this was done, a Full Import Full Sync on the source AD was able to pick up the changes which can be viewed under Filtered Connectors. In my case you can see there are 89 Filtered Deletions which are basically the result of user filters applied.

Now a Full Confirming Import on the "TargetWebService" Management Agent would delete those 89 users from Office 365.

Two more observations:
1. Condition values are not case sensitive. So if you want to filter out user account which start with svc, you don't need to be worried about case sensitivity.

2. it seems to be a delay for the deleted users to actually disappear from the Office 365 portal. so if you add new filters, and confirm that filters are applied on DirSync, you may not see the changes on the Office 365 portal immediately.

Monday, 20 May 2013

80041034a error code when a federated user tries to sign in to the Office 365 portal - "Your organization could not sign you in to this service" error

When a federated user tries to sign in to Microsoft Office 365 from a sign-in webpage whose URL starts with, authentication for that user is unsuccessful. The user receives the following error message: "Your organization could not sign you in to this service"

Tried the following resolutions suggested in KB article which did not resolve the isse in my case:
  • Resolution 1: Disable Local Security Authority (LSA) credential caching on the AD FS server
  • Resolution 2: Update the relying party trust with Windows Azure AD

This issue was resolved by converting the federated domain to standard (managed), and then converting it back to federated.

I am not sure if it was relevant to this issue (as some threads suggested), but when I initially converted my domain to federated, I had -SupportMultipleDomain switch on. I am assuming that it is not relevant because I still used the switch when I converted the managed domain to federated in the second time.

Thursday, 9 May 2013

Use PowerShell to assign specific service plan licenses to Office 365 users

You can use PowerShell to create users in Office 365 and assign licenses to them.
In order to do it you will first need to see what your Account SKU IDs are by running the following command:


This will give you a list of your available SKUs in the following format:

mydomain:SKU (Example: mydomain:ENTERPRISEPACK)

Now you can use the retrieved "AccountSkuID" to assign licenses to users. Below is an example of creating a new user and assigning E3 (ENTERPRISEPACK) license:

New-MsolUser -UserPrincipalName "" -DisplayName "Amin Test1" -FirstName "Amin" -LastName "Test1" -UsageLocation "GB" -LicenseAssignment "mydomain:ENTERPRISEPACK"

You may want to assign specific licenses within a SKU rather than assigning the whole E3 license. In that case you need to create your own license assignment option. To do that we first need to see what the service plan IDs are for each individual service within the E3 SKU. 

Run the following commands to get a list of service plan IDs:

$s = Get-MsolAccountSku | Where {$_.SkuPartNumber -eq "ENTERPRISEPACK"}

As you can see, the following are the individual service plans in E3 pack:
RMS_S_ENTERPRISE                 (Windows Azure Active Directory Rights - this is new in Wave 15)
OFFICESUBSCRIPTION              (Office Professional Plus)
MCOSTANDARD                         (Lync Online)
SHAREPOINTWAC                      (Office Web Apps)  
SHAREPOINTENTERPRISE          (SharePoint Online)
EXCHANGE_S_ENTERPRISE        (Exchange Online)

Now we create our own custom plan to assign an individual service plan license to a user. In this example we are assigning SharePoint Online license:


As you can see we still set the AccountSkuId to "mydomain:ENTERPRISEPACK", however using the DisabledPlans switch we are disabling all the other service plans, leaving SharePoint Online only.

Now that we have created our own license assignment option, we can re-run the New-MsolUser command and add our own license option to it:

New-MsolUser -UserPrincipalName "" -DisplayName "Amin Test1" -FirstName "Amin" -LastName "Test1" -UsageLocation "GB" -LicenseAssignment "mydomain:ENTERPRISEPACK" -LicenseOptions $MyLicenseAssignmentOption

On the portal we can check the license assignment status of the new user that we just created and we can see only SharePoint Online license is assigned to the user:


Tuesday, 30 April 2013

Configure Lync federation with external domains in Office 365

You can control Lync Online access to these people outside your organization:

  • Lync users in other companies    The other company must also set up federation with your domain.
  • Skype public IM service users    Signed in with their Microsoft account (formerly Windows Live ID)

Configure federation with external domains

Login to Office 365 portal using your admin credentials.
Navigate to "Lync Admin Center" by selecting Lync under Admin drop-down

Click Organization > External communications.

Under External access, choose an option that controls your access to other organizations using Lync:
  • Off completely
  • On except for blocked domains
  • On only for allowed domains
Under Blocked or allowed domains, you can Add Add, Edit Edit, Remove Delete, or Search Search the list of domains as appropriate.
Keep in mind:
  • The organization you’re federating with must also allow federation with your domain.
  • When you’re communicating with someone in a federated domain, you can only use Lync features (for example, video conversations or desktop sharing) that are turned on in both organizations.

Configure public IM connectivity

  1. Click Organization > External communications.
  2. Select the check box under Public IM connectivity, and then click Save.
 Important    Full support for communication between Lync and Skype will be available by June.
Available with Skype users today Available with Skype users by June 2013      Not available with Skype users
  • Presence
  • Person-to-person instant messaging
  • Person-to-person audio calls
  • Find and add Lync contacts in Skype
  • Video conversations
  • Multi-party IM conversations
  • Audio and video conversations with three or more people
  • Desktop and program sharing

Thursday, 28 February 2013

Windows PowerShell for SharePoint Online Reference - Part 2

You can find part 1 of this blog here:

Organization level monitoring and management

Use this command to get application errors.
Get-SPOAppErrors –ProductId ba51729b-e017-409d-681a-66f1dd18f0f4

This command will return a list of all installed applications.
Get-SPOAppInfo –Name "Excel Service" 

Returns SharePoint Online organization properties.

Retrieves SharePoint Online company logs. For now, the only logs available are for Business Connectivity Services (BCS).
$endtime = Get-SPOTenantLogLastAvailableTimeInUtc$starttime = $endTimeinUTC.AddMinutes(-1200000)$tenantlogs = Get-SPOTenantLogEntry -StartTimeinUtc $startTimeinUTC.Date -EndTimeinUTC $endTimeinUTC.Date

This command returns the time when the SharePoint Online organization logs are collected. Same as the Get-SPOTenantLogEntry command, for now, the only logs available are for Business Connectivity Services (BCS).

You can use this command to get a list of all site templates available that match a given identity.

This command sets properties on the SharePoint Online organization.
Set-SPOSite -Identity -LockState NoAccess


After your Wave 14 Office 365 tenant is upgraded to Wave 15, you will notice that your SharePoint sites are not automatically upgraded to the latest SharePoint 2013 site. You can use this command to trigger the upgrade after you have properly assessed and tested the impacts of upgrade.
Upgrade-SPOSite -Identity

and here is a reference to available parameters for this command:

As mentioned in Upgrade-SPO command, before upgrading to SharePoint 2013 in Office 365, you may want to test the impacts of the upgrade in advance. you use this command request to create a copy of an existing site collection for the purposes of validating the effects of upgrade without affecting the original site.

Reference for more reading:

Windows PowerShell for SharePoint Online Reference - Part 1

You can now use SharePoint Online Management Shell to performs administration tasks on SharePoint Online. In this article I have put together a reference to all the commands available to date for SharePoint Online with examples.

You can also use the "Windows PowerShell for SharePoint Command Builder" tool to build commands using a drag and drop interface which allows you to select and enter command parameters in a visual way. Refer to this post for more information about this tool.

Service connection and disconnection

This command is used to establish a connection to SharePoint Online Administration Center.
Connect-SPOService -Url -credential

Use this to disconnect from SharePoint Online.

User management

This coman is used to add an existing Office 365 user or an Office 365 security group to a SharePoint group.
Add-SPOUser -Site -LoginName -Group "Marketing Owners"

This command is used to return the SharePoint Online user or security group accounts that match a given search criteria.
Get-SPOUser -Site -Group "Team Site Members"
Get-SPOUser -Site -LoginName

Use this command to remove a user or a security group from a site collection or a group.
Remove-SPOUser -Site -LoginName -Group "Marketing Owners"

This can be used to configure properties of an existing user
Set-SPOUser -Site -LoginName -IsSiteCollectionAdmin $true 

User group management

Use this command to get a list of all the groups on the specified site collection.
Get-SPOSiteGroup -Site

This command can be used to create a new group in a SharePoint Online site collection.
New-SPOSiteGroup -Site -Group "Senior Marketing Staff" -PermissionLevels "Design"

Use this to remove a SharePoint Online group from a site collection.
Remove-SPOSiteGroup -Site -Identity "MarketingManagers"

This command updates the SharePoint Online owner and permission levels on a group inside a site collection.
Set-SPOSiteGroup -Site -Identity "CoolGroup" -Owner

Site collection management

Use this to get a list of deleted SharePoint sites in the Recycle Bin.
Get-SPODeletedSite -Identity

This command returns one or more site collections
Get-SPOSite -Identity

Use this to create a site collection.
New-SPOSite -Url -Owner -StorageQuota 1500 -CompatibilityLevel 15 -LocaleID 1033 -ResourceQuota 300 -Template "mytemplatename" -TimeZoneId 13 -Title "This is my new so cool site"

Use this command to get rid of the sites in the Recycle Bin.
Remove-SPODeletedSite -Identity

Use this to delete a site. After deletion site will remain in Recycle Bin.
Remove-SPOSite -Identity -NoWait

This command can be used to checks and repair a site collection and its contents.

Use this command to restore a deleted site collection from the Recycle Bin.
Restore-SPODeletedSite -Identity

Use this to set or update one or more properties for a site collection.
Set-SPOSite -Identity -StorageQuota 3000 -StorageQuotaWarningLevel 2000

Use this command to test a  site collection.

Windows PowerShell Command Builder

The Windows PowerShell Command Builder for Microsoft SharePoint 2010, Microsoft SharePoint 2013, SharePoint Online, and Microsoft Office 365 is an HTML5 application that is designed to help IT professionals and power users learn how to use Windows PowerShell for administrative tasks.

You can find the Windows PowerShell for Sharepoint Command Builder here:

or can download its guide from the following link:

Choose the product that you want to create PowerShell commands for - in this example SharePoint Online.
You have option to choose one of the following products:

  • SharePoint Online
  • SharePoint Foundation 2013
  • SharePoint Server 2013
  • SharePoint Foundation 2010
  • SharePoint Server 2010
  • Office 365

Once you have selected a product from the product list, you can drag and drop 1 verb and 1 noun from available lists on the left, to the designated area on the right.

In this example I choose "Get" as my verb and "Site" as noun:

Based on Verb and Noun that you choose, tool will present the additional parameters that you can configure for the command which will appear in "Required" and "Optional" panes.

At the end you can grab the final command from the information box on the bottom left of the page. in this example the generated command is as follows:
Get-SPOSite -Identity " " -Limit "1"

Wednesday, 30 January 2013

Office 365 SSO logon issues - Error: There was a problem accessing the site

External users report that they cannot access Office 365 services and when they are redirected to the AD FS page they get the following error:

Error: There was a problem accessing the site. Try to browse to the site again. If the problem persists, contact the administrator of the site and provide the reference number to identify the problem.










With AD FS related issues, you can usually get some useful information by running the Remote Connectivity Analyser and test SSO authentications.
To run Remote Connectivity Analyser to test SSO authentication in Office 365, follow these steps:
  1. Open a web browser, and then browse to .
  2. Click the Office 365 tab, click Microsoft Single Sign-On, and then click Next.
  3. Type your user ID and the password, click to select the security acknowledgement check box, type the verification code, and then click Perform Test.

    • Your user ID is your user principal name (UPN).
    • You must enter actual, real credentials that are associated with the Office 365 SSO implementation that you are testing.
Reviewing the result of the tool, notice that test has encountered an error when trying to retrieve and validate ADFS metadata.

This normally indicates that one or more of the services on which AD FS 2.0 response relies is unavailable in some way.

How to resolve this? in my case a good old fashioned restart of the AD FS servers sorted out the problem. :)

Monday, 28 January 2013

The New Office (next generation of Office 365) release date announced

Next generation of Office 365 known as the "New Office" seems to be available from 29th of January. check out the link below:

How does the integration between Outlook and Lync work?

Lync needs to communicate with Exchange in order to read/update the following information:
  • Create the Conversation History folder
  • Handle voice mail notifications
  • Handle missed Conversation notifications
  • Read Contacts folder
  • Find related conversations
  • Open contact card
  • Create a personal Outlook contact
  • Open voice mail
  • Write contacts (on demand) (EWS and Exchange Server 2010 SP1 only)
  • Write Conversation History items (on demand)
  • Read or delete Conversation History items
  • Read or delete voice mail items
  • Read free/busy times
  • Read Out of Office message
  • Read working hours information
  • Handle Exchange contact sync
Lync has two ways of communicating with Exchange; EWS (Exchange Web Services) and MAPI (Messaging API). EWS is only available in Exchange 2007 and above. So previous versions of Exchange (such as Exchange 2003) does not have this feature.
In order to communicate with Exchange, Lync first tries to connect through EWS, and only if EWS is not available then it will fall back to MAPI.
It is important to know that integration through MAPI does not cover all the integration features that you would get with EWS. The following are the features that are NOT available with MAPI:
  • Read or delete Conversation History items
  • Read or delete voice mail items
  • Read working hours information
  • Handle Exchange contact sync
And also with EWS you don’t get the following (this is MAPI only):
  • Communicate with Exchange delegates
Note: As I mentioned earlier, Lync tries EWS first and if it is not available then it falls back to MAPI. However as you can see, “Communicate with Exchange delegates” feature is only available through MAPI connection, so if you have EWS and MAPI in place and you notice you have connections on both, then that’s probably because you have Exchange delegates.