Configuring Yammer Dirsync

I’ve recently blogged about using DIRSYNC to connect your local Active Directory (AD) to Office 365. It is one of the most popular posts on this blog and you can find it here:

Windows Azure Active Directory Sync tool (DIRSYSNC) – the basics

I have followed this up even more recently with a post about the updated DIRSYNC tool called Azure Active Directory Sync Services and you can find that here:

Azure AD Sync Services tool – the basics

Finally, I have posted about the preview of the tool that is replace Azure AD Sync Services called Azure AD Connect and that you can find here:

Azure AD Connect (Preview) – Install

You may think these are the only tools used or required to copy you local AD to Office 365 services. They aren’t. Hopefully, you know that Yammer is now included free with many Office 365 plans and Yammer also contains user information. In fact it is possible to copy some of this user information from your local AD.

The place to start is the:

Yammer Directory Sync 3.0 Admin Guide

but before you get too far into the weeds what benefits does Yammer DIRSYNC provide?

As the guide says, after you set up this integration product, users will be able to be automatically:

– removed from your Yammer network when you disable them in AD

– invited to your Yammer network when you add them to AD

– updated with new profile information when you update their attributes in AD

and that is basically it. My personal take on this is that Yammer DIRSYNC doesn’t really provide a lot of benefit for smaller organisations that don’t have thousands of AD users and who don’t have large amounts of turnover within their staff. If that is your business or your customer’s business then you can stop reading here and not have to worry about this any more.

However, I hope that you are at least somewhat curious as to how the whole configuration process of Yammer DIRSYNC is completed, and you might also be interested in some of the ‘challenges’ I faced getting this to work. That, at least, I hope makes you read through the volume of information I’ll detail here with the process I went through.

This attempt to configure Yammer DIRSYNC was completed in a test environment. I created a new clean Office 365 E3 tenant. I installed a new clean Windows Server 2012 R2 server in Azure. I created a new set of local AD users and used AD Connect (Preview) to get them copied to the Office 365 tenant. I then assigned them licences. All of this was prior to getting Yammer DIRSYNC operational.

So the plan was now to install Yammer DIRSYNC on the same server as Azure AD Connect (Preview), which as it turns out is the Domain Controller (DC). Of course best practice should always be to install any Office 365 user syncing tool (Office 365 DIRSYNC, Azure AD Services, Azure AD Connect, etc) onto a separate members server. The same would also go for Yammer DIRSYNC, however not all businesses have this luxury when it comes to rolling out addition on premises hardware do they? Also to my mind it doesn’t make sense to roll out more on premises hardware when the real desired aim to eventually move everything to the cloud. Thus, in this case, everything will reside on the Domain Controller.

image

When a user is invited to join a Yammer network they receive an email like shown above that provides them a link to get started with Yammer. When you enable Yammer in Office 365 using this process that I also recently detailed:

Enabling Enterprise Yammer in Office 365

Users won’t automatically receive such email invitations, they just need to select the Yammer icon from their app launcher inside the Office 365 portal. Thus, if you are looking to drive Yammer adoption throughout your organisation, having an email automatically sent to new users telling them about Yammer can provide a benefit. This you can do when Yammer DIRSYNC is enabled.

The first step in enabling Yammer DIRSYNC is to create a service account to be used by the DIRSYNC process. Thus, I went into my local AD, created a new user called Yammer Service and allowed that to sync to Office 365 (as I have Office 365 DIRSYNC enabled).

An interesting question gets raised here. What securities does this Yammer service account require both on premises and in Office 365? From what I can determine, locally, the Yammer service account can be just a normal user in the local AD and in Office 365 it has to have at least a mailbox license. This means if you only have Office 365 Suite licenses (i.e. SharePoint, Exchange, Skype for Business, together) you will need to either dedicate a complete license for this service account or purchase a stand alone Exchange Online license and add this to your tenant (which you can do now as Office 365 plans allow you to mix and match plans in one tenant).

imageO

Once the Yammer service account has been created in local AD, synced to Office 365 and assigned a license you simply login as that account and then navigate to Yammer so the service account is now an activated Yammer user. All this is the normal way you create and activate any Yammer user.

The next step is to login as an existing Yammer verified admin (typically an Office 365 Global Administrator) and select the Yammer enterprise admin area. Once there you will find an Admins option as shown above. Here you promote the new Yammer service account to be a verified Yammer admin.

 

image

Doing so means that the Yammer service account will have full control over Yammer (i.e. a Yammer admin) without the need to be an Office 365 Global Administrator (which gives them full control over more that just Yammer in Office 365).

Once you have added the Yammer service account as a Yammer admin you will also need to select the Grant Verified Admin button above to give that account full rights in Yammer.

image

You should now see the Yammer service account (here called Yammer Service) appear as a Current Admin as shown above.

image

What I then tried to do was go back into the Office 365 licensing and remove the license for the Yammer service account as I wanted to conserve licenses given I was using an Office 365 suite. Problem is when you do that (i.e. assign no license) you also don’t appear to get a Yammer license. You also don’t get a mailbox license which it turns out you’ll need later.

So, any Yammer service account requires at least a mailbox license in Office 365 from what I can determine.

The next step in the process is to download the Yammer.Dirsync.Setup program to your local on premises server on which the sync is gong to take place. You can download this software from:

http://go.microsoft.com/fwlink/p/?LinkId=511986

image

You kick off the installation and change the install directory if desired. if not then it will install into:

c:\program files (x86)\yammer\directory sync\

Select the Install button to continue.

image

You’ll then see the software being installed.

image

When that process is complete you’ll see the above screen. You need to insert the Yammer service account and password in the top part of the options to the right.

Now as you can see, when I did this I received the error Unexpected login failure even though I knew the password was correct. The solution lies here:

https://support.microsoft.com/en-us/kb/3015691

Which in essence this is telling you that you need to generate a unique ‘app’ password for this account to move forward.

image

To do that you’ll need to log back into Yammer as the service account and select the three dots in the top right and then Apps from the menu that appears.

image

In the All Apps area towards the bottom of the page select the Yammer tab.

image

Locate an app and select it by name. Here I located the Windows Phone app and select the hyperlink Windows Phone.

image

This will show you something like the above. The information you require is in the lower left of this window.

image

here you should see your Yammer service account email and a temporary password. You will need to use this back with the Yammer DIRSYNC program.

Note that the app password is only available for a short period of time, so copy it from here and then immediately head back to the Yammer DIRSYNC configuration.

image

Place this Yammer app password in the password field and select the Login button to continue.

image

I next received the above message which I have no idea what it meant so I simply selected OK to continue.

image

The next step is to put in the details for your local domain. Here I specified my domain controller and select the Login button.

image

Doing so then placed my domain controller in the window. Strangely, there is no continue button so I simply selected Validate from the options on the left to proceed.

image

Now select the Start Validation button.

image

The validation process will then commence.

image

At this point I received the error:

Invalid or missing attributes for required attribute(s): mail

image

After much trial and error I discovered that the apparent reason for this validation error is because the email attribute for the user is not set in the local AD. You can see the location of the attribute in the above screen shot of a users properties in AD.

In an environment with no local Exchange server you have to wonder how this field is going to get populated? Clearly, in my case it has to be done manually. That could be quite a pain if you have a lot of users!

image

Now, with all the users in the local AD having their email field populated I could successfully complete the validation step as shown above.

Again, no real next button here so select Sync from the options on the left to continue.

image

To continue you need to enter mail server and user details as shown above. This is the reason why you need to ensure that the Yammer service account has at least an Exchange Online license.

The server in this case will be Office 365 which for SMTP is:

smtp.office365.com

Port is:

587

and Enable SSL should be checked.

A number of articles I found said that you need to ensure the FromAddress field in the EmailNotificationSettings section in the file globalsettings.config.json should be manually changed from the default of noreply@yammer.com to being the same as in the Username field above, which should be the email address of the Yammer service account.

When I searched the directory that Yammer DIRSYNC was installed but I couldn’t find the globalsettings.config.json file. Turns out it is actually located in:

C:\ProgramData\Yammer\DirSync

by default. You may, as I had to, change the default view in Windows Explorer to actually see and navigate to the directory.

image

Turns out there is now a Yammer DIRSYNC icon in the system tray that if you right mouse click on show a menu as seen above.

image

If you select About from the menu that is displayed you will see the above dialog appear.

image

If you then select the Advanced Configuration button a Windows Explorer window will be opened at the location of the globalsettings.config.json file which again is located at:

C:\ProgramData\Yammer\DirSync

You can open the json configuration file with notepad and make the appropriate change from noreply@yammer.com to the email address of the Yammer service account you are using. Close and then save the json configuration file.

image

You then return to the Yammer DIRSYNC installation program and complete all the details.

You should also then be able to select the Send Test Email button to verify everything is working.

image

After which you should receive a green check mark as shown above.

To proceed, select the Apply button to the right which should now be available.

image

The Enable Sync button at the button of the window should now be available and The Status should read Not Running as shown above.

Select the Enable Sync button to proceed.

image

You should see the Status field runs through a few options such as Validating Settings as shown above.

image

If there are no issues the Status should say Running as shown above.

image

You can close the Yammer DIRSYNC program and it will continue to run in the background. You should find a Yammer DIRSYNC icon in the system tray which you can right mouse click on and select Open from the menu that appears to view the program again if needed.

Here is the Microsoft documentation on installing the Yammer DIRSYNC application:

Install Yammer Directory Sync

Now according to this:

The Yammer Directory Sync utility now queries Active Directory every 60 minutes and adds, updates, and suspends users, as appropriate.

The log files:

  • service.log – contains sync errors

  • ui.log – contains UI errors

are located in the directory:

C:\ProgramData\Yammer\DirSync

along with the json configuration file.

image

What should happen after a a period of time is that if you look in Yammer as an admin under the Directory Integration menu option you should see that it has been enabled as you can see above.

image

If you return to the on premises server you installed Yammer DIRSYNC on you will find a service called Yammer Directory Sync 3.0 as shown above.

Now, what I found was that Yammer DIRSYNC service was taking a very long time to actually sync. This was probably due to the fact that the first sync is quite large but my overall experience is that Yammer sync is quite slow and there is now way to force it like you can with Office 365 DIRSYNC. You simply have to wait.

When I look at the service.log file after this et I was seeing an error:

INFO [2015-06-11 23:18:28,807] – Scheduled interval set to 60 minutes
INFO [2015-06-11 23:18:28,807] – Starting with sync enabled: False
INFO [2015-06-11 23:18:44,224] – IPC Server running successfully
INFO [2015-06-11 23:19:51,595] – Registering callback for Yammer.DirSync.Core.IPC.Transport.NamedPipeServerBus+CallbackReference
INFO [2015-06-11 23:20:06,842] – Changing sync enabled to True
ERROR [2015-06-11 23:20:06,880] – Error saving enabled state
System.UnauthorizedAccessException: Access to the path ‘C:\ProgramData\Yammer\DirSync\globalsettings.config.json’ is denied.
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
   at Yammer.DirSync.Core.FileSystemRepositoryBase`1.Save(T settings)
   at Yammer.DirSync.Core.FileSystemRepositoryBase`1.Save(Action`1 update)
   at Yammer.DirSync.Service.ScheduledSyncService.SetEnabled(Boolean status, Boolean interrupt)
INFO [2015-06-11 23:20:07,014] – Starting sync because sync state changed.

After another long period of troubleshooting what I found the solution that removed this access issue from the log file was changing the Yammer Directory Sync service to run as a domain administrator rather than the Network Service.

The other issue I saw a lot of in the log was:

Waiting for previously running sync to complete.

So in the end I left the sync process running and went away to do other things.

Eventually after at least 4 hours I returned to find that syncing was now successful.

INFO [2015-06-12 00:09:39,647] – Sending remote job Suspend with 1 users
INFO [2015-06-12 00:09:40,674] – Data received for job syncie-2-e2007c89-007f-44c6-8bd8-8e66b4ab6e9e, processing has begun.
INFO [2015-06-12 00:09:41,589] – Waiting for previously running sync to complete.
INFO [2015-06-12 00:49:51,074] – Yammer Directory Synchronization has completed.
1 Users Added
1 Users Updated
0 Users Suspended
0 Pending Users Deleted

I find it interesting that it took at least 4 hours to initially sink a clean demo system with only a handful of users! Again, my experience has been that Yammer DIRSYNC is quite a slow process.

INFO [2015-06-12 00:49:51,157] – Sync attempt finished with status: Success
WARN [2015-06-12 01:50:03,650] – Some attributes do not exist in directory CIAOPS-DC2: title, physicalDeliveryOfficeName, telephoneNumber, mobile, department, proxyAddresses
INFO [2015-06-12 01:50:03,774] – Reading directory users
INFO [2015-06-12 01:50:09,522] – Completed reading directory users. 0 total users.
INFO [2015-06-12 01:50:09,897] – No changes for sync phase CreateOrUpdate
INFO [2015-06-12 01:50:10,278] – No changes for sync phase Suspend
INFO [2015-06-12 01:50:10,278] – Yammer Directory Synchronization has completed.
0 Users Added
0 Users Updated
0 Users Suspended
0 Pending Users Deleted

As you see from the subsequent sync log above I was still get warnings which I wasn’t really sure what they meant or how to fix them, so I ignored them.

image

However, now after I created a new user in the local AD, allowed it sync to Office 365 via Office 365 DIRSYNC, then assign an Office 365 license, waited some more for it to sync to Yammer, the new user did receive for Yammer via email as you can see above.

Phew, that is a lot of work just to get that one email!

I then also deleted a user from the local AD, saw it removed from Office 365 and also no longer be able to login to Yammer so I am confident that the deletions in Yammer DIRSYNC also work as expected.

At this point I started to get more errors occurring with the Yammer DIRSYNC program to the point where the Yammer sync process would stop. I did some initial research on what might be causing these issues but abandoned that after a short while as I couldn’t really see much ROI in Yammer DIRSYNC.

At this point I abandoned further work on Yammer DIRSYNC as I had gotten it working.

Summary

The smaller the organisation the less of a need for considering Yammer DIRSYNC. I don’t believe it provides much real value unless you are adding or removing lots of users from you AD on a regular basis.

I found a lot of issues getting Yammer DIRSYNC operational and keeping it running in a small test environment. Maybe I overlooked some things or did stuff wrong, but I really couldn’t find a lot out there to help. I have included some helpful sites below in the references section.

It seems to me that the Yammer single sign on experience will be driven in future from Office 365 and Azure rather than a local application on a server syncing local AD. Hopefully something Azure AD Connect will one day incorporate all the synchronization Yammer requires. I expect this to be the case as Yammer becomes more and more integrated with Office 365.

The synchronisation of information to Yammer is very slow and only happens once an hour at most. I found now way to be able to force this synchronisation.

If you do have issue with Yammer DIRSYNC don’t be afraid to raise an Office 365 support ticket. The Yammer support people were very obliging and knowledgeable.

References

http://www.lifeonplanetgroove.com/setting-yammer-directory-sync-office365/

https://about.yammer.com/success/wp-content/uploads/sites/13/2013/05/Directory-Sync-3.0-Install-Guide.pdf

https://about.yammer.com/success/wp-content/uploads/sites/13/Directory-Sync-3.0-AdvancedConfig-Guide.pdf

https://jorgequestforknowledge.wordpress.com/2014/10/08/setting-up-yammer-dirsync/

http://channel9.msdn.com/Events/SharePoint-Conference/2014/SPC368

How to audit users in Yammer – https://technet.microsoft.com/en-us/library/dn783348.aspx

http://blogs.technet.com/b/askyammer/archive/2015/05/18/yammer-directory-sync.aspx

Plan for Yammer DIRSYNC – https://technet.microsoft.com/en-us/library/dn799027.aspx

Office 365 web scheduler gets a makeover

image

One of the often overlooked utilities available in Office 365 for those with a Skype for Business account, is the web scheduler. For much of its life it was branded as Lync. However, now it has had a makeover to Skype for Business branding as you can see above.

Everything is basically the same as it was before and the way you schedule meetings is identical. Any scheduled or previous Lync meeting will also still appear. It is basically a look and feel makeover.

The only think that hasn’t changed as far as I can find is the URL you use to access it, which is:

https://sched.lync.com

but I’m sure that will be changed as well soon.

For more information about this see:

Skype for Business Web Scheduler

Office 365 Saturday–Sydney

O365 Saturday Australia

I have been lucky enough to be selected to speak at the Office 365 Saturday event in Sydney this weekend, the 13th June. My session is on the ‘Business of Yammer’ but I am also looking forward to a full day of Office 365 topics presented by some very knowledgeable people in the SharePoint and Office 365 space.

One of the sessions I am really keen to see is the one on PowerBI. So if you are interesting in attending you can register at:

http://www.o365saturdayaustralia.com/Pages/Sydney.aspx

O365 Saturday Sydney kicks off registrations at 8:30am on 13th June at Cliftons – 13/60 Margaret Street, Sydney NSW, 2000.

The whole day is free and great opportunity to do some networking and get those burning Office 365 questions answered. If you are planning on attending let me know and we can perhaps catch up.

I hope to see you there.

Talent has its limits, Skill doesn’t

We tend to celebrate those who have an abundance of what appears to be “natural talent”. That is, what appears to be a natural gift for performing some task well above the average. Chances are that what is actually being witnessed is a combination of talent and skill, with skill being far and away the greater component of the two.

Why is perceived raw “talent” so celebrated? The reason probably lies in the fact that it is easier for people to digest the belief that achievement is more the result of random genetic luck outside their control than consistent individual effort. Such a belief, therefore, alleviates a requirement for hard work because success only appears to be associated with randomly winning the genetic ‘’lottery”.

The reality is that talent is certainly a gift and some people have greater talent than others, but talent has its limits. One of these limits is that you can’t accumulate more talent, you receive your allotment at birth and that is the balance you retain throughout your life.

Skill on the other hand is limitless. The more effort you are prepared to invest the more skill you will accumulate, it really is that simple. Yet there’s the rub for most people, skill requires effort. What’s more, true skill requires continued effort but is something that you can constantly build every day of your life.

Optimal results are obtained when you marry your given talent with on going skill development. I hear many times how people “can’t” when really what they are saying is they “won’t” because they are not inclined to make the effort. That attitude is nothing more than a mental block preventing them from achieving more. The distance to move from “won’t” to “want” is small, yet for many it is a barrier that never gets overcome.

Life is not a Disney movie. There is no one coming to save you and roll out the red carpet before the credits roll. That is your job. You are equipped with the physical tools to achieve anything, what prevents you doing that is only your state of mind.

So many focus on just the physical, but like your physique, your mind needs to be trained as well if it is to remain healthy. Like unused muscles, if it is not exercised regularly it withers and dies.

The question to you is then what are YOU doing to exercise your mind? What are you doing to build your mental capacity and expand your horizons, achieve your goals and live an enjoyable life? That last question seems cliché right? But ask yourself, are you honestly living an enjoyable life? Every day? I don’t find many strongly affirmative answers to that question when it gets asked.

The choice is yours. You can live a life bounded by whatever talents you have been endowed with, or you can embark on a journey of never ending opportunity and potential by regularly exercising your mind and building your skills. Even if you start way behind the “talent-only” pack, the certainty is that one day you will surpass them. It is at that point you begin to truly appreciate that the “unfair” advantage of what many equate only as “natural talent” is in fact nothing more complex than effort.

If you change “can’t” and “won’t” to “want” nothing will ever stand in your way. You, and you alone control the key to an enjoyable life by focusing on skill rather than talent.

More granular admin roles now available in Office 365

image

You should now start seeing in your Office 365 tenants the ability to set more granular administration roles for your users in Office 365 as shown above.

You’ll see all the old favourites such as Billing Administrator, User Management administrator but you’ll also now see some new ones like SharePoint and Skype for Business administrator. This allows you to delegate administration for a particular services to a particular user.

Great some more options when it comes to assigning rights with Office 365!

Azure AD Connect (Preview)–Install

In a recent post I detailed the current replacement product to DIRSYNC:

Azure AD Sync Services tool – the basic

In there I noted that this will soon be replaced with Azure AD Connect which is currently in preview:

Azure AD Connect Preview 2 is available

I thought I’d run through a short walk through experience of installing Azure AD Connect just so you can see. When the product comes out of preview I’ll do something in more detail.

image

You download and run the tool.

image

This will give you an icon on your desktop and launch the install wizard.

image

You need to agree to the license terms.

image

You select the Continue button.

image

You’ll be prompted to install any prerequisites. Press the Install button to continue.

image

You can select any custom configuration you desire. Press the Install button to continue.

image

You should now see the service commence installing by installing SQL Express as AD Sync Services did.

image

It will then start installing the Synchronization Service.

image

Next, you’ll need to enter you Office 365 credentials and select Next.

image

You should then see the connection to your tenant being made.

image

At this point you can elect to use the express settings or work through the customised options. The express options will automatically:

– Configure synchronization of identities in the current AD forest

– Configure password synchronization from on premise AD to Azure AD

– Start an initial synchronization

– Synchronize all attributes

For most standard configurations this is fine but we will select the Customize option rather than the Use express settings here to see all the options.

image

Select the Password Synchronization option and Next to continue.

image

Next, enter you on premised domain credentials and select Add Directory. If you have more local domains you can add these but normally all you need to do after adding the local domain is select Next.

image

The local AD information will be retrieved.

image

Here is where you can now elect to filter what is synchronised. Since we only have one domain we’ll elect to synchronise everything and press Next to continue.

image

Normally you select User are represented once across all directories here and press Next.

image

This option allows you to match on premise users with those in the cloud via different attributes. best practice is normally to leave the default options and select Next to continue.

image

There are lots of options here that are in preview. Select the Password writeback to sync information from you local AD to Office 365. Remember, that at the moment two way sync will not occur unless you have an Azure AD Premium subscription, which is not part of Office 365. Office 365 only includes free Azure AD.

The hope however is that when Azure AD Connect comes out of preview the ability to sync passwords from local AD to Office 365 and back will be included with all Office 365 plans. However, right here, right now for two way syncing you need an Azure AD Premium subscription.

Select Next to continue.

image

Everything is now ready to configure so press the Install button to proceed.

image

The wizard will now do its thing.

image

Configuring you Office 365.

image

Updating rules

image

The on premises domain.

image

Then enables password sync.

image

In a few moments the process will be complete and you can press Exit to end.

image

As before, you’ll find a number of new applications installed.

image

The Synchronization Service will give you the ability to monitor the progress real time.

image

if a user tries to change a password in their web portal they will be greeted with the above message basically informing them that it has to be on premises NOT in the cloud.

image

An Office 365 administrator can reset the password via the admin portal for a user but after the next sync has run from the local AD that changed password will be overwritten with the one from on premises.

Thus, there is not a huge change between what we have now with Azure AD Sync Services and what is coming with Azure AD Connect. At this stage, you still need and Azure AD Premium subscription to do password write back to on premises as well as many of the advanced features. The hope is that this will change when Azure AD Connect come out of preview. Fingers crossed.

SharePoint Online Backups

I get lots of questions about how/if data is backed up with SharePoint Online. Remember, that SharePoint Online is composed of two items , Team Sites and OneDrive for Business. Both of these are SharePoint, OneDrive for Business is simply a very limited set of standard Team Site features, but it is STILL IS SharePoint.

As I say over and over and over again, SharePoint is a collaboration system not just a file share. It is very different from a traditional network share. Thus, the way that data is stored is very different to start out with.

Firstly, all of SharePoint’s data is stored in a database. Calendars, contacts, lists AND flies are all stored inside a database because they are objects. This means that when you upload a file to SharePoint Online it is wrapped inside an object that contains additional information not just the file. This information could be meta data, workflows, previous versions and more.

When a user deletes something from SharePoint Online it will generally be sent to their recycle bin. They can recover it from here themselves currently for a period of 93 days.

If in that 93 days the file is deleted from the users recycle bin it is moved to an administrator recycle bin for the remainder of those 93 days.

Points to remember with the recycle bin:

– Deleted items can be recovered up to 93 days after deletion

– Items in the users recycle bin count against the storage quote for that site. Items in the administrators recycle bin don’t count against the storage quota for the site.

– The administrator recycle bin can only be accessed by a Site Collection Administrator.

For more information about various recycle bins and how to recover see:

Manage the Recycle Bin of a SharePoint Online site collection

Document Libraries, i.e. where files are stored in SharePoint, have version history enabled by default and set to save 500 versions of a file. Each time a file is changed and save a new copy is retained. This versioning can be edited and disabled if required and also counts against your storage site quota.

For more on versioning see:

How does versioning work in a list or library?

Apart from that SharePoint Online

– Is backed up every 12 hours and kept for 14 days

– The only recovery option is a full site collection restore

– To perform a site collection restore you must contact technical support

– The restore location is the same as the source, so you will loose all data that is currently hosted there.

Further details are contained in this blog post:

Restore options in SharePoint Online

If none of these options are adequate then there are third party backup providers like:

Leaphq

and

CloudFinder

and others that can provide an alternate method of backing up SharePoint data.

With all SharePoint Online backup option, you need to understand that some allow recovery of any items (i.e. appointment, list item, contact, file etc) while some just allow recovery of files.

In my experience, with document library versioning now enabled by default and presence of a recycle bin, there is generally no need for a third party tool, however they are available if your needs are not adequately covered by the tolls built into SharePoint.

Back with Blogger

As I mentioned a few posts ago, I and a lot of people where having problems posting from Windows Live Writer to Blogger.

After successfully post my mega-article on AD Sync Services I am happy to report that everything is back up and running as it was. For that I’d like to thank both Microsoft and Google engineers who sorted the issue out. You have made a lot of people very, very happy.

My only concern now is what is the roadmap for Blogger and Windows Live Writer? Is this just a temporary fix or will we face the same issue down the track? Unsure whether we’ll get an answer there so something to keep in mind going forward.

Again, those who listened and resolved the issue, a HUGE amount of thanks.