Microsoft Use Third Party Tool To Help Their Own Migration

In an article published by SharePoint Pro Mag, Microsoft themselves have used a third party tool to assist them with an upgrade from SharePoint 2007 to 2010.

“Just this week, it was announced that Microsoft itself, the Microsoft Technology Centers, migrated from dedicated SharePoint 2007 to SharePoint 2010 on an internal cloud hosted by MSIT (Microsoft IT), and even the MTC’s turned to a third party migration tool (by AvePoint) to migrate content to the cloud while maintaining metadata and configuration.”

I am very surprised that Microsoft has turned to a third party tool to complete their migration. I’m not sure if it’s just me, but it does not give their customers much confidence in what they (Microsoft) do, if they have to turn to another company for help regarding one of their own products. This potentially shows that using a third party tool to help with a companies migration should not be considered as shameful or cheating or using the ‘easy’ option.

The full article can be found at: SharePoint Pro Mag.

Workflows in Office 365

Workflows have so far been overlooked in this project, so we thought it was time to find out a little more about them and how they can be used. If a Workflow was to be displayed in a graphical form it would look like a flowchart. A work flow follows a series of actions to automate common processes within a business. For example we have looked at a workflow for the process of authorising annual leave. Here the user makes their request through the team site, the workflow is started automatically when the item is added, and the ‘Approver’ is then notified and asked to either approve or reject the request. If the request for annual leave is approved, the requesting user is then sent a confirmation email. If the request for annual leave is not approved then the item is deleted from the list and the requesting user is sent an email explaining this. The great part about designing workflows is that they can be designed in Microsoft Visio, in a graphical form, then exported into SharePoint Designer 2010, which then creates the overall framework for you. All that is required then is to add in the specific parts of the variables, for example who to send the emails to etc. Workflows can greatly improve speed and efficiency with common tasks, and can also save money by cutting out the small tasks that would normally be carried out by people.

Creating the workflow itself was relatively easy, the Visio file was easy imported into SharePoint Designer and the appropriate selections were made for each stage in the workflow’s journey. Unfortunately, every time we uploaded the workflow into SharePoint it would not work what so ever. The workflow is started and the list item (the holiday request) says “In progress”. When viewed, office 365 says that it may be a bit slow due to a large amount of processing, 5 minutes later that message is replace with an error message. We aren’t sure if it is something that we are doing wrong or whether the Workflow we have created just isn’t compatible with Small Business, either way, it’s frustrating.


We have since found out the following, and it appears that some of the functions that we included in the workflow are not supported by the small business version.

The following workflow actions are not supported in Office 365 for small businesses:

Start Document Set Approval Process, Capture a Version of a Document Set, Send Document Set to Repository, Set Content Approval Status of the Document Set, Start Approval Process, Start Feedback Process, Start Custom Task Process, Declare Record, Undeclare Record, Lookup Manager of a User, End Task Process, Set Content Approval Status (as author), Wait for Change in Task Process Item, Set Task Field, Rescind Task, Append Task, Delegate Task, Escalate Task, Forward Task, Insert Task, Reassign Task, Request a Change, Send Task Email.

No workaround is available. To use these SharePoint workflow actions, you must have Office 365 for enterprises.


We have now managed to get the built in workflow, three-state workflow, to work after struggling to get it to function correctly, it just previously kept failing.

Lightening Strike

A recent story that hit the news talked about how the only Amazon server for europe had been knocked out by a lightening strike. Amazon had warned it’s customers that they could be offline for up to 48 hours as they struggled to recover from the power disruption. It took 3 hours to recover from the first of the affected instances, but after 12 hours a quarter still remained offline, with knock on effects slowing their likely recovery time.

In light of this, it is of most importance to have backup plans that can be put in to place should these very unlikely natural disasters occur, or any other disasters for that matter. For instances such as lightening, a simple surge protector can do the job. If back up plans are not made and events such as fire, lightening, rioting, flooding, or power outages occur then business may not be able to trade or function, especially if everything (data) is stored in the cloud.

Further more to this issue, another article talks about how there are seven things in particular.

  1. Read your cloud provider SLA very carefully
  2. Don’t take your providers assurances for granted
  3. Most customers will forgive a company for it’s failings
  4. There are many ways you can supplement and cloud provider’s resilience
  5. Building in extra resilience comes at a cost
  6. Understanding the trade-offs helps you frame what to ask
  7. Lack of transparency may be a companies ‘Achilles Heel’

Office 365 Customer Services


We have been receiving an error in our Office 365 site for about a month now, this error denies us from editing some of the public facing site and permissions. A ticket request was opened around the same time to deal with the problem and it’s only now that we have had any reply (and that was after I sent a few angry emails), in fact I was contacted by phone. Up to this point, customer service from Office 365 had been pretty terrible due to complete lack of contact, however, Josh from Microsoft seemed eager to help and get to the bottom of the problem. Unfortunately he was not able to help from his position but he took as much information as he could and has passed it onto the next stage, he has also promised to contact the department dealing with the request every day and inform me of any changes.

In conclusion, Microsoft customer services are pretty poor when it comes to getting round to your service request but when they do, they provide a good customer service experience.


Microsoft Premier Deployment for Office 365

Microsoft Premier Deployment helps customers to make a safe and efficient transition to the cloud environment. Microsoft offer this service to Enterprise customers who plan to migrate 2,400 or more users. Microsoft offer two services, to either assist with the planning of the migration and then hand over to the organisation to implement the plan for the migration, or customers can opt to work directly with Microsoft’s deployment teams.

Microsoft will identify any issues with the computing environment that may need to be resolved to meet the requirements of Office 365 and provide a proposal to address any other gaps. To date Microsoft Premier Deployment has migrated over 2 million seats of fortune 100 customers to online services, using the standard tools their team uses.

Microsoft will also mitigate any migration and deployment risks with the help of an experienced deployment team, they will also manage your deployment budget by using a fixed price approach.