Registering a support ticket
If you have bought your licenses directly through the O365 portal, you can also create a ticket using the portal. You need to be a Global Admin or a Dynamics 365 Service Admin to place a ticket. Currently you cannot indicate that the ticket is for Dynamics so you simply write so in the text and the O365 support team will create a new Dynamics 365 ticket for you. I was amazed at how fast the Office 365 support called me after registering a ticket, I think it took less than 1 minute. So I would suggest you choose the option "call me".
If you have a partner, I strongly suggest that you register them in the Office 365 portal for the Dynamics 365 subscription as Partner of Record (PoR). This will make your company show up in their Microsoft partner portal where they can register a support ticket for you.
When registering the ticket with Microsoft, there are some things you have to note:
- Be polite. Even if your system is slower than sirup in January (a Swedish saying) or nobody can log in, you will not be getting any help faster by screaming or being rude. I like to quote my grandfather who had a good saying: "Better to be strong in argument and withheld in words, than the other way round." I have actually gotten written compliments for being nice by the support people, do you think they will go the extra mile for me?
- Be very exact with what is you think is wrong. The best way is to formulate it like this: "I did X and expected Y but I got Z". Also be clear on when you define the case as closed. This is particularly important, and hard when you have performance issues or intermittent errors. But try to be as exact as you can. For example: "When users run Chrome open a Contact (after the contact form already has been loaded for another record) it takes 10 seconds. We expect it to take no more than 2 seconds."
- Only have one issue per ticket. Better to have many tickets open. I have had 4 tickets open for one single customer at the same point in time.
- If you think the issue is important, describe it in business impact terms. For example "The bug X affects all sales people in the organization effectivly stopping them from using Dynamics 365. It severly risks our entire Dynamics 365 investment as users look at other solutions and the user adoption drops dramatically and the trust in the system is drastically lowered for every hour this bug is not fixed. We have 4354 sales people in our global sales organization spread out over 34 countries. It also affects managements abilities to manage the company as no pipleline and forecast numbers are produced which could potentially cause sever business damages that cannot easily be fixed within the coming 4-5 years." - This was just made up :) but it is important to not hold back when doing this, especially if you are Swedish or from other cultures which value humbleness.
- Be clear on limits of the error.
- Which Operating system?
- Which browsers?
- What times? Can you see any clear patterns on when it happens?
- Security roles?
- Types of users affected, AD users federated to O365 or Cloud users?
- How long?
- Which versions of Dynamics 365 are you running?
- Which instances have the issue (the url:s)?
Types of tickets
What types of tickets can be registered? Should you only register a ticket when you want help with something?
Well, no, you can and should register a ticket for many different reasons. As I mentioned at the top of the article it is important to think about Microsoft Support as your Dynamics 365 IT-department. They will help you with a lot of things that your IT-department would have helped you with had they hosted your Dynamics system. The main difference is probably that they do nothing else than host Dynamics 365, every day, year after year... not many IT-departments that can compare with that.
Typical issues they can help out with are:
- Something seems to have stopped working that used to work, and you didn't change anything. Like you cannot create an Application User anymore.
- Something clearly is a bug in Dynamics 365 and you want Microsoft to know about it (they might not know) and you want to let them know how important it is for you (they will surely not know this).
- You need some information from the Server, like the "Top 10 table Usage" report from the SQL database.
- You have performance issues.
- You need to change the planned upgrades because your team won't make the set time.
- You want to set some non-clustered indexes on the database.
- You are doing a migration of large amounts of data and you will be a bad neighbour for a few days and if possible you would like a little more than the 2 allocated threads in the API.
- You want a database copy prepared for installation into an on-prem equivalent.
- You need some detailed information on how the service is managed, like
- How backups are stored
- How to restore backups from the 90 day tape backup
- Where an instance is hosted
- You would like to move an instance to another datacenter
- You need to remove a managed solution but it has dependencies that shouldn't be there...
- You need to do some task with an instance that you cannot do yourself with the instance manager.
In other words, they will be your superfriend when working with Dynamics 365 and you want to be really nice to your super friend!
MVP, Founder and Principal Consultant at CRM-konsulterna AB