The Activity Store is the New Source of Truth

The search for a document management solution wasn’t really being undertaken by the right people until you were asked whether or not it could either

  1. Serve as the Source of Truth, or
  2. Respect another repository as the Source of Truth

Life used to be so simple back then. At least, that was how it seemed. It turned out, that even the records management solution was never The Source of Truth – it was only ONE Source of Truth within the organization.

We will forever have to manage many Sources of Truth within our information farms and fields and domains.

It was always easier, though, when we could roll up multiple systems or at least similar systems, into a single Source of Truth.

Printed circuit board futuristic serverThe lingua franca of our information domains has changed, though. It’s no longer documents, or fragments, or reusable content. It is not even the lowest common denominator, the log file, any longer. It is now “Activity”. If that sounds like a vague term, it is only vague until you define it. Create a schema for it, and then every system can feed and consume “Activity” using JSON or other protocol (I’ll bet you still have plenty of systems/applications using REST or Javascript APIs or even .CSV files, don’t you?) and your systems can start to build on each other again.

Microsoft 365, primarily through the use of the O365 Audit Log and the Microsoft Graph, is providing an Activity Store that will power the next generation of applications.

Microsoft Azure and Amazon Web Services provide solid tools for managing and tracking the IaaS portion of your data center. But there is no comparison to the Audit Log and the Microsoft Graph for making sense of what is happening within your Digital Workplace.

As you build applications, you should be dropping hints, if not writing explicit updates, into the Log and the Graph. This is not only for ISVs, but also for the new breed of custom developer, or even power users.  You can choose to make your app yet another Source of Truth, but if you want your data and function to be incorporated into one of the new style of Digital Workplaces, then you may be better served by leveraging a central Activity Store.

The Activity Store is the new Source of Truth. Are you leveraging it yet? If not, your competitor might be.  There will always be many Sources of Truth. But buyers will be asking if you are yet another, or if you are able to leverage the one that they have.

Retiring The MOSS Garden

I’m finally getting around to some summer gardening. It’s time to plow under some ground that used to be productive, in the hopes of re-planting and eventually reaping some future harvests.

I’ve retired “The MOSS Garden”, and have transplanted my historical records of blog posts from the now-retired MSDN Blog where they used to be planted, and moved them into here. Those are basically the posts from 2003 through Sep 2010.


So, if I’m going to get back into blogging, that leaves me two blogs… and (this one). I’ve never been much for search engine optimization, so it will be interesting to see if any of those old posts ever get indexed or have any views. But, at least they will have a home as my old MSDN blog is about to die. See you online!

Changing Workplace Behavior and a Focus on Intranets

I enjoyed reading Paul Miller‘s article about his predictions for the Digital Workplace for 2017.  So much so, that I decided to put down some thoughts that I couldn’t get out of my mind any other way.

Paul Miller, who leads the Digital Workplace Group, has a track record of prediction about the digital workplace over the past years. His entire article is one that I would recommend, and his entire list of ten (10) predictions for 2017 is worth considering.  Perhaps I will spout off about his other predictions at a later date, but for today, I want to tackle two of them, which are front and center with many of the Office 365 customers that I work with regularly.

Paul Miller’s Prediction #2 for the Digital Workplace

2. Focus shifts from “firing up tech” to changing behaviour and culture

This is a striking change that we in the Digital Workplace Group have seen strongly in 2016. For the first time, many large enterprises are most concerned about culture and behaviour change when deploying new digital workplace services – and are viewing turning on the technology more as a “hygiene factor”, particularly as services move relentlessly to the cloud.

For one major pharma client in Germany, their new collaboration services were straightforward technically – but after evidence from their history that simply implementing new technologies doesn’t bring the much-touted benefits to employees, this time they turned to change management and culture as the levers they needed to tackle. This pattern will extend for many organizations and the so-called “soft skills” of digital workplace improvements will take centre stage.

This is absolutely true – that companies are finding it more difficult to roll out applications and technology services to their employees and expect employees to be able to leverage them easily.  The switch in focus to encourage a cultural change among employees is a change that can’t come quickly enough.

This is a representation of the move to a SaaS-based and cloud-based infrastructure. Large application systems that previously were installed using a Big-Bang installation model were replaced by agile development and continuous deployment. Enterprise IT groups that used to deliver employee facing software applications and LOB services via large concurrent deployments are discovering the benefits of continuous deployment. The next phase of realization for this is probably with employees, that will need to transform from learning new application functionality and tools every year or two into a slipstream model of discovering new functionality weekly or monthly.

A focus on modifying culture and employee behavior will have a more productive impact on employee adoption. The tools and applications will still need to be built – and as more employees adopt the new tools, deployment cycles can perhaps shorten and the feature backlog for each app may also shorten.


I also think that Paul’s fourth (4th) prediction is worth some consideration.

4. Intranets keep getting better and stronger

Weren’t intranets supposed to have become extinct by now? Rumours of their demise have been around for 15 years or more. The reality is though that any well-functioning organization of any size still requires a robust, productive intranet, if only as a digital front door to the wider digital workplace.

Whether it is Estée Lauder or Nationwide, compelling intranets that deliver value to the workforce are essential within the context of the broader needs of digital workplaces. Upgrades, new functionality and better mobile experiences will all be part of the enhanced intranets we will see.

I also believe that the concept of Intranets is growing and deserves to be strengthened within organizations. The Employee Intranet is the heart of soul and culture for an organization. Often, as employees work in teams that are more distributed than ever, as organizations change more frequently, and as the nature of work relationships morph through time, employees will rely on the Intranet as a centering force.

It used to be that the Employee Intranet served up the published information to employees, and also provided support for work-in-process scenarios – the ad-hoc collaboration spaces for project teams and for employee workgroups. While intranets were manageable in size, this made some sense, and the cost to apply consistent branding elements across all sites was manageable.

Today, ad hoc collaboration sites find themselves being more separated from the highly structured intranet sites. Employee Intranet sites pay the cost of applying company branding to their pages, while ad hoc collaboration areas need to be spun up and down as projects are created and completed, and can’t afford to pay the “branding tax” for each instance.

I think that as the amount of separation between ad hoc collaboration areas and employee intranets continues to grow, that Intranets will gain strength and find it easier to maintain company culture and focus.

Enterprise IT Groups should consider the employee intranet as a discrete service offering from ad hoc collaboration spaces. Trying to combine them weakens the value proposition of both.


What are your predictions for Enterprise Transformation in 2017? I like Paul’s list – and will give the Digital Workplace Impact podcast a listen.

Collaboration in the Market

Atlassian and Slack each are making plays in the collaboration marketplace today. Both of these moves are in response to recent advances that Microsoft has made with Office 365 and are critical to their long term future as platforms.

By acquiring Trello, Atlassian is expanding it’s collection of collaboration services and is a stronger competitor for Office 365. Atlassian is responding to Office 365 increase in customer adoption of Planner. Trello is more mature and more feature-complete than Planner at this point in time. Atlassian has the integration game to play now, to provide customers a consistent experience across the apps. To their benefit, Trello and JIRA have been used together by developers and project teams for years, and their JIRA customer base already is mostly familiar with Trello.

Microsoft, for its part with Planner, is entering with a new product, which even at MVP was rapidly adopted by Office 365 users looking to manage tasks, but still lacks many required features to be more than a task manager for small teams.

Atlassian acquires Trello for $425M, broadening their reach ]

The second news item this morning also affects Office 365, as Slack is building out their integration with a solid investment in bot companies. This has the potential to be a good investment, as Slack is battling to find a hook into enterprise businesses. As a chat company in a crowded space, it floated to the top with great functionality, but I feel it still is sitting in a space that hasn’t fully solidified, and could be replaced by newcomers to the space, or someone that has a better integration.  With this investment in bot makers, Slack is hoping that integration with business processes can stick and become a solid connection for them to build on.

Slack invests in 11 new bot startups ]

Both of these are examples of products that are building themselves into a platform. Becoming a platform that is extensible enough for ISVs to build on top of is the key for their long term growth. If their partner ecosystems simply invest in connecting to JIRA and Slack, and don’t take the next step of building into the platforms or building on top of them, then they will get steamrolled in enterprise companies by the platform that is surrounding and embedding the collaborative applications in Office 365.



What goes around, comes around.

the-road2016 was a fun and interesting and painful and excruciating and difficult and rewarding and peaceful and disruptful year. It had a little bit of everything, …which turns out to be often how I feel about every previous year on every Jan 4th.
Lots of goals for the year to come, lots of ideas about where things could have gone better, and lots of sketches of projects that are still midflight.
I’m typing this on my new standing desk, I went to the gym yesterday, I’m on my ketogenic diet again today, and the family seems to be mostly happy and healthy, so it looks like 2017 is off to a good start.
I’m also writing a blog post. – one of those things that did not happen during the entirety of 2016. Strange, isn’t it. I started blogging in 2003 (, and I don’t think I missed an entire year since then, although my blog has gotten a little spindly from time to time as I’ve experimented with different platforms. Until 2016. My platforms of choice for 2016 were Facebook and Twitter, it seems.
I’m going to give the blog another go in 2017, though. Facebook, LinkedIn, the blog, and a Office 365 Technology site that I’m working on and hope to unwrap soon.
During the day, I continue to be helping Satya and Jeff spread the word about the productivity benefits of SharePoint and Office365 in my little corner of the world.
Always happy to talk or chat. Contact me anytime.

Cloud Hybrid Search Preview

If you are using SharePoint Server 2010 or SharePoint Server 2013 on-premises in conjunction with Office 365 and SharePoint Online, then you probably have started to tire of having a search center for your on-premises content and a separate search center for your cloud-based content.

At Microsoft Ignite (Chicago, May 2015), it was announced that a Hybrid Search Application would be shipped that would build content search indexes for your on-premises data and ship them up to SharePoint Online so that you could rely on the one search center in SharePoint Online to be the search center source of truth for all of your content.


This was released a couple of months ago, in two ways. You can find it in the cumulative updates for SharePoint Server 2013 starting in September 2015, or in the Preview release of SharePoint Server 2016.

Download link for SharePoint Server 2016 Beta 2

Start link for Cloud hybrid search capability in SharePoint Server 2013

If you are running SharePoint 2010 search today, there were a few SharePoint 2010 search features that were replaced with different features in SharePoint 2013 search and others that may have been modified for SharePoint Online search. Please check the documentation in the Cloud hybrid search download for the list of unsupported search features.

Support for SharePoint 2010 and Stefan

Two things to cover off in this blog entry.

Stefan Goßner is one the the Few and the Proud when it comes to worldwide SharePoint support.  His blog is the public entrypoint into his wisdom and experience regarding SharePoint.  (He works for Microsoft as a SharePoint Support Engineer in Germany). Please add his blog to your newsreader (or flipboard, if you are a millenial?) Stefan can be found online here:

Second, let’s finish the work with SharePoint Server 2010 byt quoting from his blog.  Still on SharePoint 2010? (extended edition).

Today is October 14th, 2015 which means that Mainstream support for SharePoint 2010 is over. SharePoint 2010 is now in extended support.

What does this mean for you as customer if you are still using SharePoint 2010?

  • We recommend to upgrade to SharePoint 2013.
  • Only security related hotfixes will be created for SharePoint 2010. Any other problems in our product will not be fixed (except for customers who purchased xtended Hotfix Support through Premier Support).
  • Support cases which are caused by problems in our product will no longer be free of charge.
  • You will still get paid-support (including pay-per-incident Premier and Essential Support) through Microsoft Customer Support Services.
  • You can still get product-specific information using the online Microsoft Knowledge Base or Support site at Microsoft Help and Support to find answers to technical questions

For more details see our Microsoft Support Lifecycle Policy FAQ:

OK, now that we have that out of the way, back to our regularly scheduled programming.