During my years working with Dynamics Online Installations there has been questions asked by different clients in regards to the numbers in the URL and where their data is stored? This mainly signifies the location of the data centre where your data is stored and here is a list of the current Dynamics 365 Online regions: North America (crm.dynamics.com) South America (crm2.dynamics.com) Canada (crm3.dynamics.com) EMEA (crm4.dynamics.com) APAC (crm5.dynamics.com) Australia (crm6.dynamics.com) Japan (crm7.dynamics.com) India (crm8.dynamics.com) North America 2-for Government (crm9.dynamics.com) United Kingdom (crm11.dynamics.com) Microsoft Cloud Germany (crm.microsoftdynamics.de) As Microsoft's Cloud offerings grows l highly recommend you keep checking the folowing Microsoft site for more up to date information as more data centres are for sure to be used: https://www.microsoft.com/en-us/trustcenter/privacy/where-your-data-is-located

This is a tool generated internally to help you isolate an issue you may have with your system and in the event you raise a support case with Microsoft for a quick prompt resolution l would recommend providing this information Why run the diagnostic tool? The tool will help speed up the process of data collection and identifying issues. What is the point in collecting Diagnostic Tool Logs? If you are compentent in reading these logs by all means do so but if not raise a support case with Microsoft and share all of the data that has been collected when running the diagnostic tool. This will help Microsoft compare their findings against a list of known issues, configuration issues, and other problem areas. If turns out that these are logged on their database, this will be flagged to the engineer assisting and can potentially resolve the issue much faster than investing a lot of time a lot of time try different things. By using the diagnostic to collect the information, this can

Network performance is a key factor to understand better on how Dynamics365 Application performs responds and user experience.For several years now l hear from users located remotely in different regions complaining that the Dynamics365 application is loading slowly. There could be several other reasons, there are several methods to test network performance. CRM by default offers this diagnostics tool since back in the day of CRM 4 to check Dynamics365 application performance. This diagnostic tool helps produces a simple yet useful report on bandwidth, latency and JavaScript rending performance. This diagnostic page will issue series of pings from client (User machine) to server (Dynamics365) and transfer several batches of data. Based on this data it will provide the latency in milliseconds and max transfer speed achieved. This is a quick and easy to identify the network performance without having to install any tools on client or server. It helps us to gather some baseline perform

A few friends have been looking at a few methods to get all the details of all scheduled reports on the SSRS Server on an on-prem deployment.Here is simple SQL query which will give you details on report subscription along with Subscription type, render format, next run date, time, email ID configured with subscription etc.  Please Note: You need to run this SQL Query on your report server database. SELECT c.Name AS ReportName, 'Next Run Date' = CASE next_run_date WHEN 0 THEN null ELSE substring(convert(varchar(15),next_run_date),1,4) + '/' + substring(convert(varchar(15),next_run_date),5,2) + '/' + substring(convert(varchar(15),next_run_date),7,2) END, 'Next Run Time' = isnull(CASE len(next_run_time) WHEN 3 THEN cast('00:0' + Left(right(next_run_time,3),1) +':' + right(next_run_time,2) as char (8)) WHEN 4 THEN cast('00:' + Left(right(next_run_time,4),2) +':' + right(next_run_time,2) as char (8)) WHEN

Field Level Security (FLS) is a great feature which allows you to lock down certain fields to specific users or teams. You can control who can read the data, create the data and edit the data. This allows administrators to account for many security needs. For more detailed information on Field Level Security review this TechNet documentation. It is also a good idea to use solutions when moving customizations and this includes customizations to your security model and security settings. These are areas that can greatly impact users so they always should be tested in a development environment if possible. Here are some things to keep in mind when moving Field Level Security Profiles between environments: The field must have FLS enabled before the FLS Profile can be updated. This means your release process must be a 2 step process: (1) Import a solution containing the field and publish, then (2) Import a solution containing the FLS profile and publish. If all is contained in one

It can be overwhelming when getting started using workflows and other processes in Dynamics 365. So let's start by breaking down the types of processes that are available and how you might use these. When creating a Process from the Settings -> Processes area you have 4 options: Action - An Action is a set of steps configured by a CRM Administrator and then called through code (such as a plugin). This allows you to have an Administrator control the business logic but the developer could determine when that logic is used This is something to consider when you have limited access to a developer so you can minimize your dependence on them For example - You could have a Plugin firing when a task is added to a queue and it calls an Action to assign it to the manager. The Plugin could determine when it needs to fire, but the Action could control how the manager was set. Business Process Flow - Business Process Flows allow you to create the ribbon across the top of a reco