I could have posted this in the Dynamics 365 forum, but I'm looking for some feedback in the AX community, instead.
As most of you know, as of November 1st, 2016, Microsoft is switching their branding of Dynamics AX (or Dynamics AX Online or Dynamics AX 7) to Microsoft Dynamics 365 for Enterprise Operations App. While this abundance of words is confusing anyways, it's additionally confusing because of the additional offerings in the non-enterprise space. In addition to Microsoft Dynamics 365 for Enterprise there's also a Microsoft Dynamics 365 for Business. The "for Business" offering is intended for companies in the <250 employee ranges and the "for Enterprise" offering is for greater than that.
If I want to write a tweet, or a post, or have an in-person discussion with someone, the only way to be specific enough is to use the full name, which costs 52 characters. We need a way to shorten this, but still be accurate. I recently ran into an issue with some "for Business" folks on Twitter where I wasn't specific enough and people started getting confused.
What do people think? Is the Kelly Kane-initiated #D3FO hashtag good enough? Does it need an "E" for the enterprise piece (#D3FEO)? Let me know what you think. I tried having this discussion on Twitter, but I kept running out of characters!
Yep I think that is the name. But for those customers who, say, are looking at using the "sales" app for D365 there will need to be a differentiation of Business vs. Enterprise. Continued along that line of thinking, Microsoft puts out marketing like is seen in this picture, and they don't mention which apps are on the Business side or the Enterprise side, and it's likely confusion will grow. I agree completely that no one is "throwing away" anything. It just adds that much more work to explain all of this to new customers, and could deter some customers when they see a slide like this clearly calling out financials as Maderia and operations as AX.
Ultimately, I completely agree with your sentiment Martin. There's still a lot of dust to settle before I stop calling it AX.
What do you (those of you other thank Jake) think of this hashtag guide I put together? https://www.dynamicconsulting.com/microsoft-dynamics-hashtags/