Posts

Showing posts with the label Process workloads

PL 400 : authenticate to the Microsoft Power Platform by using managed identities (Process workloads)

Image
Password security is a major challenge in the current environment. The development of software has reached every corner of the people where the management of passwords and identities is a major challenge. People try to have a password that is easily memorable and is the same for each access to the software. Such a situation makes the identity of the user more vulnerable. To solve such a situation, expertise has come up with the new concept called break glass. Break glass refers to a quick means for a person who does not have access privileges to certain information to gain access when it is necessary. Microsoft has been implemented similar concept in the Azure environment as Azure Active directory privileged identity management which provides a service that enables us to manage, control and monitor  access to important resources of organization. These resources include Power Platform, azure resources and others. Managed identities provides an identity for applications to use when c...

PL 400 : configure scheduled and event-driven function triggers in Azure Functions (Process workloads)

Image
Certainly, Azure Functions is true example of serverless which provides the abstraction of servers with cost effective. In the cloud concept, developer concentrates on the code rather server management. Although, it describes as unit of logical code, it divides in the three different piece, which assists it to work efficiently. There are three key components of Azure Functions: Function App : Unit of development (can have many functions). Triggers : Event source that starts the function (One per functions) Bindings :  Input : Data that is pulled in at the start an execution. Output : Data that pushed out after execution. All components are important in Azure Functions, but Triggers make it to run Azure Functions and Binding is the way to declaratively associate another resource. Triggers and bindings let us avoid hardcoding access to other services. Triggers and bindings are defined differently depending on the language of development. Those languages depend on function.json. A tri...

PL 400 : process long-running operations by using Azure Functions (Process workloads)

Image
Serverless is beautiful concept in cloud computing where developer focus on business logic instead of taking care of infrastructure as well as it is cost effective as it bills on pay as per performance. The most interesting fact is that Serverless aka Azure Functions supports many programming languages. In the article, we are going to explain about long running operations using Azure Functions. If you would like to know more about Azure Functions, please click here . Azure functions execute event-driven serverless code with an end-to-end development experience : Microsoft Azure Functions have a shorter execution time period and the default time out is 5 minutes, but Azure functions with HTTP triggers have to respond in less than four minutes, but this can be increased to ten minutes as well. Serverless function is stateless, so developers need to maintain state. Because of these limitations, Azure Functions is not suitable for long running process operations. Azure functions provides ...