Document360 is one of the leading knowledge base platforms in the market, with over 1000 enterprise customers. The initial version of Document360 was released in the year 2017. Due to the simple and elegant user experience and competitive feature set, it gained the traction of many customers in the market, leaving it to become one of the category’s top tools.

In this blog, we look at the importance of viewing Azure end-to-end transactions from the perspective of a business user, the overall benefit of Business Application Monitoring, and how Serverless360 BAM can help your organization by providing business insights in your Azure integration transactions.

In my last blog post, I discussed How you could access runtime settings like the Subscription Id or the Resource Group in Logic App Consumption. I mentioned there that this differs from Consumption to Standard since they have different engines. So today, in this second part, we are going to address: How to access runtime settings inside Logic App Standard.

We often speak to organizations about Azure and one of the common questions is what is the difference between App Insights and Log Analytics. In this article we will aim to discuss those differences and overlaps. If we think about the Azure Monitoring Platform / ecosystem, then Log Analytics and App Insights both play a role within that platform as shown below. Log Analytics plays a role in the storage of Log Data and the analysis of Log Data.

In my last blog post, I discussed securing our Logic App. I may return to this topic in the future, but for now, let’s get back once again to developer tricks and tips, and this time to address something that I’m always considering using on my solutions: How to access runtime settings like the Subscription Id or the Resource Group.

Today I’m going to continue to speak about how to Protect your Logic Apps. But today we are going to address how you can Secure data in the run history by using obfuscation.

2022 was all about Azure enthusiasts, to whom we constantly strive to deliver breakthrough features for Azure management and impart knowledge with valuable content in collaboration with industry experts. Now, we are glad to bring you all our achievements of the past year.

We have recently added the API Monitoring feature to Serverless360 and this opens up a wide range of monitoring opportunities. The principle of API Monitor is that you have an API endpoint that you want Serverless360 to periodically call and then you will make assertions against the response to check if the API is healthy or not.

In a previous article, I discussed how you could use API Management as a proxy for the Serverless360 BAM API. In the real world, I have used this approach a few times because I prefer it to the custom connectors that you can use with Logic Apps which are sometimes painful to use from a DevOps perspective and have known performance limitations that can affect the latency and throughput for connections Logic Apps make to Cloud Services.

Enterprise use of Microsoft’s Azure Cloud Services is expanding at an unprecedented rate as cloud computing usage expands. However, enterprises that have recently switched to Azure continue to have serious concerns about Azure cost efficiency. Managing the costs associated with Azure cloud infrastructure differs from reducing the cost of an on-premises server because Azure cloud infrastructure can be built as needed, typically outside the control of a traditional IT department.