Exactly one year after the announcement we find ourselves in situation that may seem quite confusing to the casual observer. There are new releases in the horizon on a continuous basis and it’s easy to lose track of what exactly is meant by which update. Well, here’s my shot at explaining what’s going on.

What’s the “R” in R8?

R8 means Release 8. OK, so what are the previous seven versions then? They don’t refer to CRM 1.0, 1.2, 3.0, 4.0 or 2011 (there never was a 2.0, as some of you will remember). This R-based naming policy comes from the CRM Online product, which used to have its own release schedule with no UR’s and a slightly different code base from the on-premises product. The first R was presumably released when CRM Online was announced in April 2008. Things changed when Microsoft Dynamics CRM 2011 was released on January 15th, 2011, after which both the Online and on-premises version have pretty much gone hand in hand.

The “Rx” naming signifies a new functionality release and should never be used to refer to Update Rollup versions. Don’t shorten UR8 to R8, because the two are not the same (even though they are intertwined as we’ll later see). The Update Rollup version numbers always start from 1, so there’s been an Update Rollup 1 for both Dynamics CRM 2011, CRM 4.0 as well as CRM 3.0. Makes googling for information all the more merrier, eh? The Rx releases are a product of the cloud era and until we reach the next era beyond cloud apps, I don’t expect Microsoft to start the numbers from R1 all over again.

What’s the Q2 2012 Service Update?

Since it would have been confusing for on-prem customers to first release Microsoft Dynamics CRM 2011, then follow it up with a “Release 7″ all of a sudden, Microsoft decided to come up with a different naming policy for these new, agile releases. Unfortunately, the naming policy they chose gave us monsters like “Microsoft Dynamics CRM 2011 Q4 2011 Service Update”. Wow, how catchy, and only 50 characters long! As a result of this, what was originally supposed to be just internal jargon became the preferred option for human communication and we learned to know the update as R7. 50 vs. 2 chars, which one would you expect to fly in the age of Twitter? ‘Nuff said.

Most of you must surely be already familiar with the contents of R8, the next release, and if you’re not, here’s a link to the Release Preview Guide. The real catch is in how the promised new features will actually be delivered. The correct answers to this question are:

• In multiple Update Rollup versions
• As solution files
• Through Microsoft hosted, subscription based services or 3rd party licensing
• In other Microsoft products

A, B, C, D – tick ‘em all. This is the reason why there will not be any single place where you can “download R8″.

What will the Update Rollup 9 contain?

The official release announcement of Q2 2012 Service Update will most likely coincide with Update Rollup 9. However, if you study the contents of the Guide, you’ll find features that have already been released before UR9. Rapid View Forms were introduced in March as part of UR7 and re-labelled as Read-Optimized Forms. The same is true for SQL Server 2012 compatibility.

As we know from the previous R7 release, Activity Feeds are delivered as a solution package that you will need to download from the Dynamics Marketplace and configure manually. The Activity Feeds solution is not a part of the “core” Dynamics CRM product. However, there are parts of it that have been built into the platform, which is why at least Update Rollup 5 is required in order to install the solution. Similarly, you will need to get an updated version of the Activity Feeds solution after installing Update Rollup 9, otherwise you won’t see the new features.

A key deliverable of Update Rollup 9 will be the cross-browser compatibility that makes Dynamics CRM available on Chrome, Firefox and Safari. Since this is such a significant change to the platform, Microsoft has been kind enough to grant access to the R8 beta release for anyone who’s willing to follow these steps. Please note that the beta bits available for download cannot be upgraded to the final release of R8, so use them in a test environment only.

Extended browser support is completely separate from the mobile device support promised in R8. While you will be able to run CRM on an iPad Safari browser, the mobile UI demoed by Microsoft in numerous occasions is only available as 1) a subscription service from Microsoft, if you’re running Online or IFD, or 2) a perpetual license to be purchased from CWR Mobility if you intend to host the required service on your own server. Trying to access your Dynamics CRM environment after UR9 installation with an iPhone will most likely just give you the simplified Mobile Express user interface already familiar from the CRM 4.0 days.

Oh, and do note that the Microsoft Dynamics CRM Mobile released for Windows Phone 7 back in Q4 2011 Service Update is a completely separate product, even though it carries exactly the same name as the new offering developed by CWR Mobility and later on re-labelled by Microsoft. Since CWR Mobility didn’t have a Windows Phone client, this mobile app will likely remain on a separate development roadmap from the CWR-based offering.

What’s the role of SQL Server 2012 in all this?

If you haven’t seen the cool drag & drop report designer or the animated bubble chart demo of Power View, take a look at this video:

Wow, wouldn’t that look nice on a Dynamics CRM dashboard! Well, even though Power View is listed as one of the R8 features, there’s a couple things you should know:

• It’s not available in the cloud. Sorry, CRM Online users. Maybe in R9 then?
• CRM dashboards are a different data visualization technique that will remain “as is” for R8, not integrated with Power View.

In addition, if you plan to use SQL Server 2012 for hosting your Dynamics CRM database and Reporting Services, it’s good to know that you can’t achieve this configuration with the RTM bits for Dynamics CRM 2011. Update Rollup 6 has established a new baseline for CRM and you’ll need to download the server installation files from Microsoft Download Center, otherwise you’ll run into the following error while trying to install the Reporting Extensions:

Unable to validate SQL Server Reporting Services Report Server installation. Please check that it is correctly installed on the local machine.

What time is Metro?

Putting things into perspective, Dynamics CRM is a small fish in the tank compared to the big whale that is Windows 8. Since R8 will be out well before Windows 8, there isn’t yet a 100% support provided for the Internet Explorer 10 browser provided with it. Hopefully the remaining issues will be addressed by upcoming UR’s as Windows 8 is nevertheless just around the corner. Presumably we’ll see a proper Metro app for Dynamics CRM once R9 is released later this year. After all, the Windows RT tablets will not be able to run Outlook and we’ll need some solution for activity tracking to and from CRM.

When it comes to Windows Server 8, official support has not been announced. However, that doesn’t mean you couldn’t install Dynamics CRM 2011 Server on a Windows 8. Daniel Cai has done just that and offers a tutorial for anyone wanting to test R8 on the very latest Microsoft products available.

More supported browsers & devices will inevitably mean more work for CRM developers, as testing your application on IE alone will no longer be enough. As we get closer to R8 go-live before the end of Q2, the need for more detailed information on the practical implications is surely growing. Luckily XRM Virtual had managed to get Karun Krishna from Microsoft to give a webinar on the topic of cross-browser development on May 1st. The Live Meeting recording is now available for viewing at the XRM Virtual site. Apparently also Karun’s slides were shared during the live session, but since the recording didn’t contain them, I decided to write down a few notes of mine from the contents of the presentation.

First up is the detailed browser support matrix seen below, which expands the list previously provided in the R8 release preview guide. Included are new yellow boxes for Internet Explorer 10 on Windows 7 and Windows 8, which indicate a “supported but not full fidelity” user experience for Dynamics CRM. Also the Firefox support on Mac OS X appears to have fallen onto this level where some display/functionality bugs will exist.

In his presentation, Karun explained that while the CRM team tried to use HTML5 compliant techniques wherever possible, there were still some areas where an alternative approach had to be used in order to replicate the existing Dynamics CRM functionality across non-IE browsers. Any IE specific APIs have been removed, but as the w3C standards are still evolving, there isn’t necessarily always one single right way to implement a specific functionality in the cross-browser world. Therefore a feature detection approach for checking for browser capability differences is recommended over developing for any specific browser version. The webinar included examples and best practices on API’s and XML processing, so be sure to view the recording for details.

It was announced already earlier that using browsers other than Internet Explorer for the administration and customization menus of Dynamics CRM would not be supported. Sorry guys, you’ll still need to boot into Windows on your MacBook if you intend to do any customization work. Some additional information was now provided on features that will not be supported on other browsers than IE. These include:

• Workplace calendar
• Services (scheduling) and service calendar
• Editors for workflows and dialogs
• Lync based presence information

One thing to note is that the old crmForm object API from CRM 4.0 days will continue to work only for Internet Explorer. Therefore if you have any scripts in place that have not been updated to use the Xrm.Page methods, these won’t work for users on Chrome, Safari or Firefox.

Finally, while iPad 2 support with iOS 5 is provided, it’s important to note that this is simply the support for usage through Safari browser, not a dedicated application optimized for the tablet environment. For the premium UX you’ll need to acquire/subscribe to an add-on app like the Microsoft Dynamics CRM Mobile for iPad, of which you can view screenshots in this post. The browser experience on an iPad 2 will have the following known limitations/issues:

• No popus. Since Dynamics CRM by default opens a wealth of windows and dialogs, this doesn’t match well with the “flat” UI’s of tablet apps.
• Touch events compared to mouse events will cause some lack of functionality (no right click, double click)
• iFrame scroll bars may be missing.
• Window closing has issues due to a focus related bug in the .close API
• No Silverlight. Well, no surprise there…

Edit 9.5.2012: The long awaited R8 release for Microsoft Dynamics CRM 2011 is now available as a beta version! PartnerSource login is required for the beta program sign-up and download (CustomerSource might also work) at http://bit.ly/crmr8beta. If you want to test your Dynamics CRM solutions in a cross-browser environment (Safari, Chrome, Firefox) before the official release of Update Rollup 9, then this is the program for you. Please note that the beta version of R8 will not support an upgrade to the final version of R8, so you should apply it to a dedicated test environment only.

Storage cost

Due to some recent announcements on pricing & functionality related updates in Microsoft’s cloud based services in April 2012, I decided to do a little comparison of storage costs between three services. SkyDrive, a consumer focused product that has very recently acquired Dropbpx-like skills of synchronizing content from one or more client PC’s (or mobile devices) into the cloud. SharePoint Online, the SaaS edition of Microsoft’s collaboration / content management platform that’s currently licensed to around 125 million business users around the world in all it’s editions. Finally, CRM Online, the Microsoft hosted version of Dynamics CRM. All of these products include some base level quota for storage, but since the subscription prices per user are not really comparable due to the application functionality included in each, I’ve instead chosen to compare what is the cost of an additional 50 GB storage on each service.

See the percentage difference in the table when compared to SkyDrive? While a pure file system storage service in the cloud for consumers is practically free these days, as we move towards more structured databases with metadata and workflow related functionality wrapped around the file, things tend to get more expensive. SharePoint Online has just recently cut it’s storage prices by a whopping 92%, yet it remains almost five times as expensive as SkyDrive. Since the price per GB on Dynamics CRM Online has not changed (at least yet), CRM in turn is 50 times as expensive as SharePoint Online. (Note: storage space ain’t cheap on other cloud based CRM systems either, including Salesforce.com).

Ok, so maybe you’re managing your own servers and SAN’s, which means the direct cost per GB isn’t dramatically different between file shares and database blobs. Let’s look at some application level features that will affect your CRM users nonetheless.

Search experience

If we put our files into a structured database that has lots of customer information already, surely that makes them easier to discover when needed? Well, to some extent it does, but not necessarily the way you’d expect. “Did I attach that document to an account, opportunity or contract?” When it comes to Dynamics CRM, you’ll need to be able to answer this question before performing your search, as there is no out-of-the-box way to perform search across multiple entities. Also, instead of entering a natural search phrase like “online migration scribe”, you’ll need to build your query one parameter at a time in Advanced Find, specifying which values should be found in which field or related entity.

Chances are you found this blog post through Google. That’s the way us humans tend to find what we’re looking for nowadays: free text searches on whichever keywords we have in our minds, rather than selecting a combination of attribute values that correspond to the parent object of the file we are after. Oh, and in case you wanted to search for text from inside the document, forget about it. Attachment contents is not indexed in Dynamics CRM, only fields on the entities directly are available for the search tools.

Editing experience

Do you ever need to revise the documents you’ve once created? Having the file as an attachment on a CRM record doesn’t quite give you the same kind of flexibility as a network drive or a document management system. You can’t directly open a document from the system into your MS Word, start editing it and save the changes. Rather you’ll need to store it temporarily on your local hard drive, then upload it back to CRM. The number of clicks and dialog windows involved in the process will not exactly encourage your end users to share information through CRM if they need to go through these steps repeatedly.

How about archiving different revisions of the document? Let’s not even go there, at least with CRM alone.

What should we do with our files then?

While it’s certainly not the end all, be all solution for document management, you should definitely give SharePoint a go and see if it delivers the type of functionality your CRM users would benefit from. The built-in integration between Dynamics CRM 2011 and SharePoint 2010/Online removes much of the pain points mentioned above. Even though it may not cover all the customer document management scenarios directly (access rights, custom folder/site structures etc.), storing files in SharePoint document libraries instead of Dynamics CRM will automatically help you address many of the aforementioned issues related to content search, storage and editing. Also, the CRM SDK provides further extension points for SharePoint document management functionality development, combination with SharePoint’s extension points. You can see an example of such a scenario in this post on the CRM Consultancy blog.

Thanks to the cloud version of SharePoint Online supporting Dynamics CRM integration starting from November last year, you can easily test the document management functionality in your existing Dynamics CRM 2011 / Online environment by signing up for an Office 365 trial account. With Office 365 E package subscriptions starting at € 7.25 per user per month, even if you’d use the whole subscription for nothing more than complementing the functionality of your CRM system, the cost wouldn’t be all that high, just 18% of a CRM Online subscription price.

Better yet, if you sign up for Office 365 first and then later on purchase CRM Online, you’ll gain the luxury of using a single Microsoft Online login across both systems (see this post for the steps). Others will need to keep using Windows Live ID for Dynamics CRM until the transition to a single platform on Microsoft’s end has been completed sometime in the future.

Even though the primary purpose of the site is for me to personally keep track of interesting links that I may need to come back to later on, there are also other people who have discovered the site, most likely through a search engine. One day I was looking at the statistics that WordPress.com collects and thought that this actually provides an interesting view to what the Dynamics CRM online community is currently searching for. In the spirit of open data, I decided to publish a snapshot of the website visit stats to show what’s hot in CRM right now and also promote some of the most useful tools and apps out there, to help more people discover them. So, without further ado, here’s the list of…

Most popular Microsoft Dynamics CRM links, Q1 2012

1. Auto Number for Microsoft Dynamics CRM 2011
2. Hierarchical Treeview for Dynamics CRM 2011
3. CRM 2011 User Settings Utility
4. Ribbon Workbench for Dynamics CRM 2011
5. MS CRM 2011 Twitter Integration by Pragmasys
6. MS CRM 2011 Pragma Toolkit: Ribbon, Sitemap Editor
7. CRM 2011 TreeView for Dependent Picklist
8. Silverlight CRM Attachment Image
9. KingswaySoft SSIS Integration Toolkit for Microsoft Dynamics CRM
10. CRM 2011 Visio add-in: Business Unit Org Chart
11. Ribbon Editor for Microsoft Dynamics CRM 2011
12. Dynamics CRM Dashboard for Microsoft Lync by Orbit One
13. Powertrak In-line Editable Grids for Microsoft Dynamics CRM 2011
14. Metadata Document Generator for Microsoft Dynamics CRM 2011
15. CRM 2011 Attribute Mapping
16. CozyRoc SSIS+ with Dynamics CRM Connection Manager
17. CRM 2011 Attachment Image Browser HTML Web Resource
18. Skype Connector Tool for Microsoft Dynamics CRM 2011
19. Bing Maps Browser for Microsoft Dynamics CRM 2011
20. Dynamics CRM 2011 Script# Xrm.Page library
21. Web Resources Manager for Microsoft Dynamics CRM 2011

There we have it, the most in-demand apps or tools for Dynamics CRM! Just don’t take the list ranking too seriously, as this isn’t a very scientific way to analyze the true popularity of the links. Some of them have been published earlier, some during Q1. Some have better keywords for search engine optimization. The page view volumes are quite limited, as the top page received 145 hits during three months. Nevertheless, I think the data still gives a fairly realistic view of the functionality people working with Microsoft Dynamics CRM are typically searching for, such as:

• Auto-numbering
• Hierarchical data visualization
• Ribbon & sitemap editing tools
• Displaying images on forms
• VoIP integration (Lync & Skype)
• Customization documentation generator

One way to look at it would be that these are all features/areas where Microsoft could improve the out-of-the-box functionality that Dynamics CRM 2011 delivers. Luckily there’s an active ecosystem around the platform that is creating either commercial or free solutions to address these areas. Especially the open source tools on CodePlex or free code samples published on various CRM expert blogs are highly valuable resources that I’m thankful for, which is why I attempt to do my own little part by sharing the best links with others. I encourage you all to do the same.

Life would be easy if you could just set up and publish your duplicate detection rules once during the initial configuration of your Dynamics CRM production environment, thus stopping the unintentional entry of duplicate records into the customer database. However, you may run into a situation where a rule that you’ve once published has later on returned to an unpublished state. “What? Who touched my duplicate detection settings?”

The likely answer to the question is “You did, but unintentionally”. You see, the duplicate detection rules are sensitive to changes in your entity customizations. As noted in the Madrona Solutions Group blog article, whenever any entity metadata is changed, all duplicate detection rules associated with that entity are unpublished.

If you look at this from the system’s perspective, the process does make sense. After all, you might have set up a duplicate detection rule that is comparing records based on a criteria that that references fields you’ve changed or removed as a part of your CRM customization actions. Still, the fact that a publish event on a CRM 2011 solution triggers an unpublish event somewhere else is not very intuitive and most system administrators are likely to be unaware of the impact. As a result, there are certainly several production CRM environments out there where the once carefully planned duplicate detection rules have been deactivated because of this dependency between solutions and duplicate detection. In fact, you might want to check your own Dynamics CRM environment right now and check if you see duplicate detection rules with the status reason “unpublished” which should in fact be published.

What this means in practice is that anyone who’s deploying solution updates to an environment that is using duplicate detection rules needs to instructed to always re-enable the rules after they’ve updated customizations that reference an entity which is being monitored for duplicates. In my opinion, it would be very practical to have the system notify you about this task, for example by asking “would you like to re-publish the affected duplicate detection rules?” when publishing a solution. If you would like to see this functionality changed in a future version of Dynamics CRM, please sign in to Microsoft Connect with your Windows Live ID and vote for the item “Automatically re-publish duplicate detection rules after deploying a solution”. Thanks for your contribution.

Keynote

The opening keynote is where the stage is set for the rest of the event, so watching the live broadcast on Monday was definitely on my agenda. Sure, it’s all about building up hype for your products by telling how great you’ve done so far, how excited you are about your future roadmap and showing off with future concept demos that have little to do with the current reality. So what! You need a little show business alongside your business applications conference.

Having the luxury of my PC keyboard & mouse at my disposal during the event allowed me to experiment with Storify, a social media storytelling tool. I captured the best tweets, photos and screenshots during the keynote and compiled them into my Convergence 2012 story. If you’re anything like me, the mental barrier for sitting down and watching a recorded conference event for 1.5 hours is quite high, so why not glance through the highlights of the show on the Storify summary? After that, you can decide if you want to read the full transcript or watch the recording on the Virtual Convergence site.

Some notes picked up from the opening keynote included:

• The Dynamics CRM momentum now stands at 2,250,000 users in 33,000 customer organizations.
• “There are no happy Siebel customers in the world, there just aren’t.” - COO Kevin Turner on Microsofts internal journey from Siebel to Dynamics CRM.
• Nearly half of the deals won by Microsoft over Salesforce.com have been due to the on-premises option and the hybrid model.

Metro

It’s Windows reimagined time all across Redmond now as we’re nearing the launch of Windows 8 later this year. This means everything that can be shown as a Metro style app running on a tablet, will be shown precisely that way. The fictional Contoso Electronics scenario of the big keynote demo used a highly customized UI built for the retail store experience only. A much more interesting demo was the project management Metro app that looked so realistic you could imagine it becoming an actual UI to some future Microsoft product to be rolled out at Windows 8 launch.

We didn’t get any official screenshots of a Dynamics CRM Metro app yet, but luckily Garth Knutson was able to snap & tweet this picture of a UI concept presented in one of the sessions. Just imagine if assigning users onto a Dynamics CRM opportunity record would look like this, how much higher would the user adoption of a CRM system be among sales people? Ah, CRM reimagined…

But the road to metro is paved with Apples. The actual tablet product Microsoft had to show at Convergence was the Dynamics CRM Mobile client for iPad, which meant that Apple devices were well presented in many of the Convergence sessions. Funnily enough, during the conference an internal email leak revealed that Microsoft was banning the use of company budget to buy any Apple products for its Sales, Marketing, Services, IT, & Operations Group. Oh well, guess we won’t be seeing many iPads on stage anymore in the following events. For those of you who haven’t seen the current client yet (developed by CWR Mobility), see my previous post on Microsoft Dynamics CRM Mobile iPad screenshots.

An important aspect to note is that the move towards Metro apps and tablet devices does also have an impact on traditional desktop usage of Dynamics CRM. Back in November I speculated that the legacy of Outlook could not be carried over to the world of Windows 8 tablets in its existing form. Since then this assumption has only been enforced by the announcement of Windows on ARM (WOA) tablets with no classic Windows application support and no sign of Outlook in the list of Office apps promised for these “iPad killers”. What this means is that the functionality exclusive to Dynamics CRM Outlook client must be moved to the cloud. At Convergence, the following functionality was more or less revealed to be included in the R9 release later this year:

• Direct synchronization of activities through Exchange (instead of Outlook)
• Support for “track in CRM” functionality in Outlook Web Access (OWA client)

Woo-hoo! It’s been a long time coming, but to me this is a clear sign that Dynamics CRM is definitely on the right track in terms of becoming more compatible with the habits of today’s mobile workforce; how they manage their activities and messages on multiple clients, not just the single Outlook on their work laptop. Making the CRM features available through new channels, such as the Office 15 Agaves, is very important for making Dynamics CRM a relevant tool for knowledge sharing as the applications and devices surrounding it are evolving.

Marketing

The biggest announcement for me personally was that Silverpop is acquiring CoreMotives. I’ve been both a customer and a partner of their Marketing Suite and all I can say is big congratulations to Rhett & Jeremie (the founding team)! You’ve done an awesome job in building the first truly integrated solution for online marketing to leverage the XRM capabilities that Dynamics CRM provides. I’m sure the product will only continue to improve and deliver even more value to the 800+ customers out there.

Despite of the acquisition, Silverpop doesn’t intend to give up on building their own integration between Dynamics CRM and their Engage platform. Another big marketing automation vendor, Marketo, also launched their integration to Dynamics CRM. Both companies have been big on the Salesforce.com scene, but obviously there’s been more and more demand for Microsoft’s platform from the types of accounts that traditionally invest in standalone marketing applications like these.

So, which route should you as a CRM customer take then? Go for a native Dynamics CRM solution like CoreMotives or ClickDimensions, or choose an integrated, external platform like Silverpop Engage or Marketo? There probably isn’t a single right answer. If you know the Dynamics CRM product/platform well and are comfortable with workflows, Advanced Find and view/chart customizations, you can get a really big bang for the buck by investing in a native solution that builds on top of your existing business application. If, on the other hand, your marketing people are not currently working with Dynamics CRM and you foresee the need to grow beyond capabilities that are a natural fit for tight CRM integration (just because it can be done through Dynamics CRM, doesn’t always mean it’s the optimal choice), you might want to investigate these new alternative offerings as well.

Social

All hail the social business, or ignore it at your peril. Already in the opening keynote, Kirill talked about the inevitable shift from systems of record towards systems of engagement that provide the tools needed for improving productivity in modern knowledge work. While Microsoft has seemed to be slow to make moves on the social front, but recent reports give indication that they intend to make significant investments to ride the social enterprise wave, on their own terms. Instead of producing individual tools for the social component, it will rather be baked into every application, one way or another.

We already knew that the upcoming R9 release of Dynamics CRM would finally contain functionality that extends beyond internal communities at work and into the great wide open that is the public social networks. The only question was, what was this thing going to run on? Now we know the answer to that, it’s InsideView. Not only will there be some level of free solutions available for download (there has in fact been a free version for over a year now), but their service will actually be integrated into the core product of Dynamics CRM. There doesn’t seem to be much details out there yet about what to expect, but functionality such as promoting information from an external network into the internal CRM Activity Feeds has mentioned as an upcoming feature.

How relevant is InsideView then for non-US markets? Time will tell. Currently they have been working on expanding their database coverage to the UK & Ireland, so let’s hope their success continues and we see the service reach out to new markets soon. In the meantime, almost everyone in B2B around the globe is using LinkedIn. Luckily enough, it was also announced during a Convergence CRM general session that a solution offering LinkedIn integration with Dynamics CRM would be released to the Dynamics Marketplace “next week” (meaning end of March). Built around the LinkedIn Sales Navigator service (starting at €29/user/month), the feature set will likely be similar to the Salesforce.com counterpart described in this SlideShare presentation.

Other forms of data enrichment also remain as bullets on Microsoft’s slides, with talks about Azure Data Market and the likes, but I haven’t seen much concrete evidence on those. Social customer care, as in “how to turn a tweet into a case record”, will be on the R9 roadmap, potentially leveraging the current Social Analytics experiment on SQL Azure. There’s no shortage of interesting existing tools on the social front at Microsoft (for example, did you know about So.cl, the social search engine?), so the question will really be how they manage to turn all these features and experiments into a product offering that their customers understand and are able to leverage in their day-to-day business.

Cloud

This is the least surprising theme of all. We already know Microsoft is all in the cloud, but rather than forcing everyone to jump in there with them, the hybrid cloud option remains their strategic differentiator.

Richard Seroter posted a collection of numbers and facts on Microsoft’s Online services, which I definitely recommend you to read. Here’s a small sample of those:

• 1,000 servers running CRM Online in 6 data centers around the globe
• 0 seconds of service downtime required for releasing system updates

As a customer, that’s what you get for €40/user/month. How does your own server room stack up in comparison? The economies of scale with services like CRM Online are hard to compete against. Especially when the company operating the service is also developing the applications it is running, with the help of 30.000 engineers on duty for cloud related development work.

Dynamics CRM has been in the clouds for “ages” already, so the biggest attention was on when would Dynamics ERP catch up. Both NAV 2013 and GP 2013 will be available on Azure before the end of the year, and AX will make it there in the next major version. Eventually also CRM Online and Office 365 will move from their current environments to run on Azure, but details on the schedule or implications to the services have not been announced.

While it’s never easy to upgrade CRM systems that contain lots of custom code and integrate to back-end systems and online marketing tools, the situation is hardly any easier on the ERP side, quite the contrary. Since also the Dynamics ERP products have now adopted an agile release policy, with new versions coming once a year, some customers are inevitably asking “in whose interest is this speed of change?” While it’s certainly cool to see demos of NAV running on a web client, deployed in Azure, operated through a Metro style app and even used while wearing your gloves, thanks to Microsoft Kinect sensor integration, surely not everyone is jumping for joy when the ERP system they were used to upgrading maybe only once per decade is now rolling out new features every year and moving onto tablets and clouds.

Speaking of the cloud, access to Dynamics CRM Online data from external applications is about to get easier with R9, if this rumor about OAuth support for the CRM OData endpoint is true. Now we just need OAuth support on other Microsoft apps like PowerPivot and the cloud data sources will soon start to catch up with their on-premises counterparts in terms of BI and integration feature set.

Summary

After the Dynamics CRM Q2 2012 Release Preview Guide was made available during Extreme CRM 2012 Berlin, there obviously wasn’t so much completely new information to be published by Microsoft at Convergence 2012 anymore. The same demos that were shown to 470 attendees in Berlin must have been reused as content to be displayed to the 10,225 attendees at Convergence, but of course that doesn’t lower the significance of these new developments. The speed of change in the Dynamics CRM world isn’t slowing down and it looks like there will increasingly be also new & updated functionality available between the bi-annual R8, R9 etc. releases. This means that you can no longer just attend one conference event per year and expect to keep up with what’s new in the product you are selling, developing for or working with.

Nowadays, just because you didn’t travel, doesn’t mean you couldn’t publish an album of “travel pictures”. As some of you may have heard, Pinterest is perhaps the hottest social network right now, and an event like Convergence finally gave me a good excuse to try the service in action. So, if you want to catch an overview of what was presented in Houston, why not check out my Convergence 2012 pinboard.

Convergence 2013 will be held in New Orleans, at the same dates as this year’s event. Be sure to mark the date on your calendar and turn to #CONV13 if you can’t make it there in person.

Sitemap & Dashboards

As we know, the “new” client is actually a rebranded version of the CWR Mobility client for Dynamics CRM. The UI looks almost identical, apart from a new set of Metro style entity icons. The sharp edges and “authentically digital” appearance look somewhat out of place in the otherwise iOS-style app, but let’s hope that there will be a full Metro app for Dynamics CRM available once the Windows 8 tablets hit the stores.

Dashboards appear to be close to the web UI as far as charts go. If you have other types of web resources on your dashboard (say, a Silverlight component), the results may be a bit less so. Also, I’m assuming entity grids will not be rendered on the iPad Dashboard, at least not in their original format.

Views

The iPad UI does support filtering data through views, just like you do on the web client. However, the views themselves will not be presented in the familiar grid style with columns, rather you’ll see a list of records with the primary field and some other data stacked on top of each other. Whether this is because of iOS limitations or an inherited design from the iPhone app, I’m not sure.

Forms

The standard fields are presented on a form that has a single column. Picklist and date fields use native iOS controls, also field types like phone numbers or email addresses will open native apps for respective actions. Why an iPad app shows you the options to dial a phone call or send SMS, I don’t know, because at least my iPad won’t allow me to do those without jailbreaking the device, but maybe Ruben has a special version of the Apple tablet

As you can see from the form, it’s not specifically optimized for landscape mode viewing on a tablet, but rather looks like a big iPhone app. Entity forms with many columns will therefore be presented as a long list the user has to scroll up & down.

Maps

As a funny little detail that Ruben mentions on the video how the account address opens up on Google Maps. Why not Bing Maps? Well, because the native map application on an iOS device comes from Google…

Off-topic: It’s great that the mobile clients for iOS, Android and Windows Phone now have the basic address mapping integration in place, now we just need to get it for the web and Outlook clients as well. While the integration itself is technically quite trivial, the requirement for purchasing a Bing Maps license for using the map data on a non-public application is currently a big barrier in the desktop world. But enough about that, let’s get back to the mobile client.

Related records

Because the sitemap navigation pane is permanently visible on the left hand side of the screen, which on a normal web client entity form would show the related records, in the mobile client these are accessed through a button on the lower right corner of the screen. Subgrid type of functionality is not available on the tablet UI, which can make it a bit cumbersome to navigate through long hierarchies of records. As a result, using the iPad client for tasks such as order entry while on the road is not really optimal in the Microsoft Dynamics CRM Mobile client. These types of use cases will still be better met with a custom developed tablet application equipped with specific data entry screens, so toolkits like Resco will remain relevant even after this official Dynamics CRM iPad client gets released.

Configuration

The mobile client is not just an alternative UI for CRM, but there is a wealth of management options for user and client management, synchronization settings, usage reports etc. Since the way you use a mobile/tablet application is quite different from the normal desktop client usage scenario, it’s important that the information presented to the user can be optimized. Microsoft Dynamics CRM Mobile allows you to do this by defining different user groups and assigning them tailored mobile profiles containing only relevant entities in the sitemap. Also the contents of the mobile forms can be adjusted, so you don’t have to show all the tens of attributes that your entities contain.

Conclusions

The CRM Anywhere theme is definitely a step in the right direction for Microsoft Dynamics CRM to become an application that truly “works the way you do”. Even though the cross-browser compatibility will enable users to open up the CRM web client on their iPad Safari browser, for any serious work on a tablet you’ll want to have a client that is optimized for:

1. touch based user interface
2. streamlined data presentation to support the “working in short bursts” mode of mobile device usage
3. offline access for those moments when 3G or WiFi just doesn’t reach you

For the subscription price of $30 per user per month (or the perpetual license you can still acquire from CWR Mobility), you can install a fully capable Dynamics CRM mobile client on both your iPad and your iPhone, and still have one user license left for trying out the latest Android phone (whether the non-offline Windows Phone 7 client will consume a license, I don’t know yet).

You can read more of my thoughts on Microsoft Dynamics CRM Mobile on this article I wrote after the announcement at eXtreme CRM 2012 Berlin.

Originally launched in the Q4 2011 Service Update (R7), the Activity Feeds solution is about to receive some enhancements in the upcoming R8 release that will allow users to better filter the content of their wall and also click “like” on posts. (Note: contrary to some comments, the “unlike” feature will most likely be simply the undo action of “like”, rather than a real “thumbs down” reaction.) Compared to other social business applications like Yammer, there still doesn’t seem to be built-in support for features such as groups or hashtags that we’ve come accustomed to use on many platforms. I’ve already written about a DIY approach for leveraging custom groups to follow posts on specific topics. Next, I thought I’d see how we could make use of the hashtag concept in Dynamics CRM.

What’s a #hashtag & what’s it good for?

Whether you’re an active Twitter user or not, it’s likely you’ve come across a person using the # sign in his or her online writing. What started out as a user driven policy of grouping tweets has later turned into a whole movement that’s gotten both users as well as commercial entities get very interested on following, measuring and encouraging the use of #hashtags on social media channels.

Twitter allows the users to click on hashtags turned into hyperlinks, thus enabling them to view all recent posts containing the same hashtag. Although Dynamics CRM is a flexible platform for LoB application development, tweaking the default Activity Feeds solution web resources to support this kind of filter functionality wouldn’t be exactly a walk in the park. However, we can certainly explore the concept and see what else the platform might have available for us that could make the Activity Feeds more intelligent. Hmm, how about workflows?

While the post box on a wall doesn’t currently allow us to include any other “magic characters” apart from the @ symbol used for performing mentions, the pound sign does have one clear advantage: it’s rarely used for other purposes than a hashtag (you might have the occasional shouts of “we are #1!” by excited sales reps appear on the wall after they close a deal, but that’s about it). This means we can quite safely use the # symbol as an identifier for our own little magic words.

Triggering processes from wall posts

Suppose you’re browsing through your personal wall on a Windows Phone 7.5 mobile while sipping on a Venti Latte at Starbucks, utilizing the free Microsoft Dynamics CRM Mobile app. You spot an item in your feed that you want to take note for further action once you’re back at your office desk. How are you going to do that?

While an email inbox is hardly a good way to manage a list of open tasks, Activity Feeds are even worse as action items, because they’re not even meant to be persistent records with read/unread status or flags/categories. The stream flows on as other CRM users perform actions such as winning opportunities and solving support incidents, which means that the item you spotted while enjoying your coffee may well be buried into the depths of history the next time you glance at your wall. Posts are merely notifications about something, not the object itself.

Instead of resorting to disconnected manual notes, what you could do is track the regarding record of the interesting wall post as a new task on your own list of CRM activities. All we need is the creation of a very simple workflow rule to achieve this. Create a new workflow process on the Post entity and mark it to be started whenever a new Post record is created.

What the hashtag concept will be used for is evaluating the content of a Post and seeing if the workflow process should be run or not. In our example, let’s use the hashtag #task to identify a Post which we would like to trigger the creation of a new task record. You might also want to check that the Post source is Manual Post instead of Auto Post (more about that later).

In your workflow rule definition, create a new task record and insert the contents of your post in the subject line. Set the regarding field to be the RegardingObjectId of the Post, owner as the person who created the Post, and a due date of 1 Day After Created On. Save your process, activate it and you’re all set.

Just type #task and let the system take care of the rest

In our example, we’ve spotted a Post regarding a new opportunity record. (Ok, so we’re doing this from the web client and not the mobile one, since believe it or not, screen capture on WP7 requires an unlocked device!) We want to mark an action item on the record for us, so we post a new item on the record wall, using the hashtag we defined: “#task Ask Chris for customer references”. Please note that simply commenting a Post will not trigger a workflow, since the PostComment entity is not available for workflows (bummer), so make sure to type a completely new Post on the item of interest.

After the Post is submitted to CRM database, the workflow is triggered and a new task will have been created on you My Activities view in a matter of seconds. Should you ignore your CRM list once you return to the office (shame on you!), the due date reminder we set on the task will cause your Outlook (and probably also your mobile phone) to alert you about the action item you created for yourself.

Drive any process with #hashtags

As you might know, the free mobile client does not allow you to create or update any CRM records, you can only read them on your mobile phone (unless you want to open the somewhat less pretty Mobile Express client). The only exception is Activity Feed Posts, which you can type on your Windows Mobile device and get the data updated into CRM in real time. Together with the creative use of hashtags and workflow processes, we can actually trigger also some other data entry and updates while on the road, as you saw from the #task example.

While you can’t create a workflow that would update the parent object of the Post, you can create new child items for it. In the example below, we’re creating a new case by using the #case hashtag.

The steps of the workflow process configuration are as follows:

• Check if the Post contains the text #case
• Create a new case record, set the title to post text, set customer as the RegardingObjectId(Post)
• Create a queue item for the new case and move it to the Support queue for CSR’s to start working on
• Wait for the case status to change from active to something else
• Create a new post on the customer wall, containing a summary of the information recorded on the case after its creation
• To finish the process with confidence on both sides, also send a direct email to the person who initiated the case creation with his/her wall post

A final word of warning: since you probably don’t want a workflow generated Post to trigger any new workflows accidentally, it’s a good idea to always set the right Post Source value (Auto Post, Manual Post) and also filter these in your workflow conditions. As an example, if you post “#case Customer asks for refund” and then later on use it as the case title that gets inserted into a new Post, you’ll soon be stuck in a loop of each case resolution creating a new case…

Internet Explorer market share peaked in 2003, when 95% of all Internet usage was on IE. Coincidentally, Microsoft CRM 1.0 was released in January 2003. At the time, providing support for any other browser than your in-house product would have certainly sounded like a requirement you could de-prioritize. Today Internet Explorer commands a market share of less than 40%. There are now more iPads sold than any brand of desktop PCs combined. If that doesn’t signal the move to a post-PC era, I don’t know what does. If you’d be a company manufacturing an IE only product for PCs in the year 2012, you could soon be out of business.

This is a fate Microsoft intends to avoid, which is why the cross-browser support for Microsoft Dynamics CRM was officially announced in the Q2 2012 Service Update release preview guide, released at the beginning of Extreme CRM 2012 conference in Berlin. We had already seen the promise of non-IE browser clients for Dynamics CRM presented in Microsoft’s May 2011 Statement of Direction and now we finally have details about what to expect in Dynamics CRM R8 release exactly one year later. As with my previous post on mobile CRM, I won’t rephrase all the content of the official announcement but I’ll rather try and reflect on the topic with some personal observations and thoughts.

There’s Supported and then there’s “supported”

If you’ve glanced at the table of supported browser and OS combinations, you’ll have noticed that Microsoft does not guarantee support on every browser out there on every operating system. This is not too surprising, as any web application developer surely knows what a nightmare the differences in interpretation of web standards between various browsers can be for application development and testing. In the words of Craig Dewar (Director of Product Management for MSDYNCRM), browser testing is a “gigantic effort” for Microsoft, which is why official support is not all encompassing.

Just because a browser or OS is not listed in Microsoft’s documentation as supported, doesn’t mean Dynamics CRM won’t work on it. So, even though there are no supported options for using Microsoft Dynamics CRM on Linux, you might not notice any problems if you access it with Firefox on Ubuntu. In fact, Craig mentioned in his keynote at Extreme CRM 2012 Berlin that even if you’re using a client that’s not officially supported, Microsoft will allow you to open support tickets on issues that are not specific to the browser/OS combination you’re running. I guess you’ll just want to have at least one Win/IE or Mac/Safari device around to make sure you can reproduce the issue when dealing with Microsoft Support representatives.

“Macbooks for everyone!”

In case you’ve been drooling over the cool Apple hardware that all the opinion leaders seem to carry with them these days, the future does indeed look brighter for people working on/with Dynamics CRM. Before you jump head first into the OSX & iOS world and format all your Windows partitions, it’s important to remember that what Microsoft is talking about here is just the browser client support for CRM end users.

While you can get Microsoft Office for OSX and run Outlook on you Mac, what you can’t do is use the Microsoft Dynamics CRM for Outlook client. This means you can’t track emails to CRM, synchronize your calendar appointments between Outlook and CRM, get CRM task and call reminders from your Outlook, synchronize your contacts from CRM to Outlook to your iPhone, or have any offline support for CRM data and application functionality when your Macbook doesn’t have WiFi or 3G data connectivity. All in all, you lose quite a bit of that seamless productivity tools magic that Dynamics CRM promises to deliver for all Windows users. I haven’t seen any announcements about a CRM Outlook client for Mac, so it’s pretty safe to assume that we won’t see one released for the Outlook 2011 for Mac version currently available.

OK, so how about the support of Apple’s mobile devices then? It says Dynamics CRM will run on iPad 2 with iOS 5.x, so that should at least deliver the full flavor of the browser experience on a tablet, right? Well, the problem is you might get more than you bargained for in that deal, since (as far as I’m aware of) the browser client will look and work exactly the same on all supported platforms and devices. If you’ve ever tried running the Dynamics CRM web client on a Windows 7 tablet, you’ll know that simply replacing the mouse cursor with your index finger will not magically “touchify” the user experience. What works nicely on a 24″ screen with mouse & keyboard input may not scale/transform into the tablet environment of 10″ screens and touch UI. If you’ve used a remote desktop app on your iPad, then I’d imagine this is pretty much what you can expect from a browser client on an iPad. Unless you go for the $30 per month subscription of Microsoft Dynamics CRM Mobile app or purchase a perpetual license from CWR Mobility, TenDigits or other ISV’s that develop mobile clients optimized specifically for the touch UI. The same goes for Android tablets, only with the exception that the browser client falls into the “not officially supported” territory.

Finally, if you’re not only using Dynamics CRM but also administering or customizing it, I’ve read that you’ll still need Internet Explorer in order to access these areas in the web client.

‘Reimagining’ Windows, should we also reimagine Dynamics CRM?

It’s important to note that the web client coming out in Q2 2012 is not a HTML5 product, rather it’s a trimmed version of the previous IE only client with removed dependencies on Microsoft’s proprietary extensions that only IE supports (.htc files etc.). The future is not here yet, but there is little doubt on the direction Microsoft is heading towards, with the upcoming WinRT framework and the big push for HTML, Javascript and CSS as the foundation for future Windows apps.

Which brings us to Silverlight. It’s been widely speculated that Silverlight 5 released at the end of 2011 will be the last of it’s kind, the end of the road. Porting existing Silverlight apps to run on Win RT is said to be easy, which should naturally be in the interest of Microsoft to ensure. As I’m not a developer, I’m looking at the discussion more from the point of view of someone who needs to examine all the available technologies out there, evaluate how they fit together and build a working business solution out of them. From this perspective, there are some concerns regarding Silverlight that very much affect Dynamics CRM users as well.

While Dynamics CRM might work on a browser/OS combination that is not officially supported, the game is different if you’re using Silverlight web parts in your CRM. If a Silverlight plugin is not available for the client, it will not work, period. This includes combinations such as Chrome/OSX, any machine running Linux and most notably the iPad. Ok, so what about making the same UI with a different technology, like HTML, Javascript and CSS? In theory everything should work on every platform in this case. You’re free to draw your conclusions on which approach is better for starting your next Dynamics CRM add-on project.

Looking further ahead to Windows 8, we’ve already received the announcement that there will actually be a completely different edition of the operating system, called Windows On ARM (WOA), that will the basis for building always on, always connected, low power consumption devices to rival the iPad. The Internet Explorer 10 browser on WOA will not allow any plug-ins whatsoever, be it Flash or Silverlight. Furthermore, the Office 15 package that is available for WOA tablets will include only Word, Excel, PowerPoint and OneNote, but not Outlook. By now you should have figured out that the Microsoft Dynamics CRM experience on WOA will need to be quite different from what we have on Windows 7 today.

If there will not be Outlook on the “real” Windows tablets, what does the future hold for the CRM Outlook client? I previously wrote about the legacy of Outlook and how it will be increasingly more difficult to carry all that legacy when moving to the Post-PC era of iPad-esque devices for every knowledge worker. By the looks of things, Outlook could possibly get split into Metro Mail, Contacts and Calendar apps. If this happens, then it’s easy to envision a separate Dynamics CRM Metro app sitting alongside them, integrating into all the other installed apps through a simple share contract. After all, isn’t that the way it should really be? Link contacts/friends/followers from any social network app to CRM contacts, track any type of status update/post/tweet from the same app as a custom activity type into your CRM database. There’s no reason why customer relationship management tasks should be any more complex or inflexible than that.

It’s great to have Dynamics CRM available soon on (almost) any browser. Still, if Microsoft truly is reimagining Windows the way they claim to be and if their business customers buy into their new story, perhaps running Dynamics CRM on Safari won’t seem all that exciting anymore this time next year.

Every consultant knows that Microsoft’s initial offering, the Dynamics CRM Mobile Express client, wasn’t really something you wanted to draw the customers’ attention to. It was just barely good enough to tick the feature box of “yes, we have mobile CRM”. On a non-touch smartphone like the popular business products from Nokia or RIM the user experience might have matched the native apps and device capabilities, but in the age of the iPhone this wasn’t at all what the users had come to expect from their mobile apps.

When Microsoft released the new Windows Phone 7 client application in CRM R7 release (2011 Q4 Service Update), we saw a glimpse of a brighter mobile future, but there was still hardly reason for true celebration. Ok, so we had a mobile optimized client now available, but it had it’s issues:

• Only available for one niche (yet growing) smartphone platform
• No ability to create or update any CRM records (except Activity Feed posts)
• No offline support

The path towards a credible mobile offering would have been quite long for Microsoft to walk all on its own. Therefore it wasn’t really a surprise that they chose to team up with an existing partner and rebrand their mobile applications and services to the new “CRM Anywhere” solution (which is still officially called Microsoft Dynamics CRM Mobile). Out of all the possible mobile CRM ISV’s out there, their partner of choice turned out to be CWR Mobility.

This could of course be seen as a big blow to the other Dynamics CRM mobile ISV’s, who now have to compete against Microsoft’s own offering. However, in the long term this may actually be a positive turn of events for the whole ecosystem. The fact that there will be an official mobile app available from Microsoft to all the major smartphone platforms will surely drive up customer awareness as well as interest towards the possible use cases for “CRM on the road”.

Considering how much talk there’s been around the mobile use of CRM applications in the past few years, in my opinion we haven’t yet seen it really bloom the way many of us would have expected it to. I think one of the reasons is that mobile CRM has often been considered mainly as “CRM lite” that offers a subset of the features the full application delivers, for those awkward moments when your “CRM full” is not available to you. If mobile CRM is an optional feature that does not tie into the processes you absolutely need to execute, how likely is it that companies will choose to invest in such an additional cost factor? Ben Mitchell from TenDigits said it really well in his presentation:

“You’ve got a perfectly working address book on your phone already. If that’s all you’re trying to replace with mobile CRM, it’s always going to be too expensive. Always attach the price of a mobile CRM solution to the business value the customer is trying to achieve by deploying the solution. Mobile functionality pricing must be delivered in the context of business objectives, not just as a last minute addition to the quotation.”

Mobile CRM is like Social CRM in this sense: companies know why they need to embrace it sooner or later, but they’re still having difficulties in articulating exactly how they plan to go about it. As the limitations of available software are quickly fading away, the focus on real life use cases must rise on top. No, mobile CRM isn’t just about replicating the desktop experience on a smaller device. It must support the mode of working in infrequent bursts and dealing with specific scenarios, such as order entry or survey answer recording while the user is at the customer’s site. The UI needs to be optimized for the process in question, not just equipped with big icons to be poked with your fingers. Whether it’s going to be packaged apps like the Microsoft Dynamics CRM Mobile growing beyond their current feature sets in customizability, platforms like the Resco Mobile CRM Studio gaining popularity as the basis for mobile app development, or even a future release of a HTML5 compliant version of the core Dynamics CRM browser app stealing the show with responsive web design, the playing field for a true CRM Anywhere solution that takes the “mobile first” thinking into everyday practice still looks wide open to me.

One interesting thing to keep an eye on is what’s going to happen to the Microsoft developed Windows Phone 7 CRM client. The R8 release preview guide states that there will not yet be offline functionality available for Windows Phone devices when the new service launches. This means that Microsoft Dynamics CRM will initially work better on pretty much any other mobile platforms compared to Microsoft Windows Phone 7 (doh!). I’m assuming that the current client version will receive some minor feature updates (new Activity Feeds filters etc.) but a full integration into the CWR Mobile platform will take more time. I’ve noticed in some occasions the WP7 client has actually been referred to as the “Activity Feeds Mobile App”, but I’m not sure if Microsoft could get away with renaming product X to product Y, then launching a new product X and charging extra money for it.

This leads us to the pricing model. Whereas the Windows Phone 7 client is a free download from the Marketplace, the CWR clients are based on a subscription fee. A company who buys licenses for Dynamics CRM, be it on-premises or CRM Online, will not receive any mobile client functionality as a part of the core product. Microsoft Dynamics CRM Mobile will therefore remain as an add-on that customers must purchase licenses for separately. Considering the price is $30 per user per month, compared to the base product price of CRM Online of $44, this means in many cases not all CRM users will be given mobile client licenses. Or perhaps they’ll just be given a midprice Windows Phone device, such as the Nokia Lumia 710, and access to the free WP7 version of Dynamics CRM Mobile. With a number of Dynamics CRM apps already out there in iOS and Android marketplaces that any user can purchase for themselves and point it to a CRM Online or IFD organization, I’m not even sure companies can effectively standardize on a single official mobile app anymore, thanks to the BYOD culture and shadow IT.

The official Microsoft Dynamics CRM Mobile service won’t be able to match the 40 markets / 41 languages level of the core CRM product, as it will initially be available only in 24 markets and 10 languages. The explanation offered by Microsoft was that there are such regulatory limitations for mobile services in many markets that they simply can’t roll out their mobile CRM offering as quickly as a cloud app like CRM Online. We’ll see how fast they can catch up and bring the service to markets like Finland. It will also be interesting to see whether the initial unavailability will simply mean the lack of local languages or if MS will actually not offer the mobile app for download at all in these tier 2 regions’ marketplaces. I sure hope it won’t be the latter option, even if it would mean I’d have to temporarily return from WP7 to Android for doing proper presales demos of the new mobile service with offline capability. The sacrifices one needs to make for the love of CRM…