Today I want to talk about a new interesting set of telemetry signals related to page views that, starting from version 16.3, Dynamics 365 Business Central is sending to Azure Application Insights.
Business Central comes with a set of API’s that you can access from other applications. When running BC in Azure you can choose between basic authentication and Oath 2.0. The latter is preferable since the requesting app does not need to store user name and password. The user will input these when giving consent for the app to access the BC API’s. The problem with Oath 2.0 is that you receive a token for access that expires.
After my last webcast about Azure Functions, I received an interesting question: how can I quickly deploy a function to Azure? Or maybe to different Azure subscriptions or regions?
We saw in the webcast how you can deploy an Azure Function by using Visual Studio or Visual Studio Code directly. But Azure Functions have also a full range of continuous deployment and integration options provided by Azure App Service and you can deploy an Azure Function directly from a CI/CD pipeline in Azure DevOps. But there’s also a quickest way in my opinion: Zip deployment.
In my last post I showed how to connect SQL Server Profiler up to a Power BI Premium dataset but I didn’t give you any examples of why this might be useful. In this post I’ll show you how you can use a Profiler trace to visualise all the queries run by a Power BI report, see when they start to run, see which ones run in parallel with each other and see what the overall time taken to run all the queries is.