I have clear a understanding on this topic as i recently deployed same action for MYOB when trigger invoice it automatically goes to the customer Nifan from Sri lanka
Hi Sir, Thanks for your effort. I have doubt in this. I understand the service principal is help to authenticate with Azure. If suppose we are running application that needs to access Azure resources and also it is hosting outside of Azure, that time only need service principal? and Is there any alternative way in azure like access key id and secret access key in AWS to access resource in AWS?
Thank you for your question! You're correct that a service principal is used to authenticate with Azure, especially when an application needs to access Azure resources. If your application is hosted outside of Azure, using a service principal is a common approach to securely authenticate and access resources in Azure. However, if your application is running within Azure, you might consider using a Managed Identity instead, (new video is coming) which simplifies the process by automatically handling the identity management for you without needing to manage credentials like a service principal. Regarding your comparison with AWS, the closest alternative would be Azure's Shared Access Signatures (SAS) or Application registration or API key or the use of Azure Active Directory (AD) for more fine-grained control. Each of these methods has its use cases, depending on the level of security and control you need. Hope this helps.
Hi Bhai, Once again Thank you very much for your time and efforts ..
I have clear a understanding on this topic as i recently deployed same action for MYOB when trigger invoice it automatically goes to the customer
Nifan from Sri lanka
Hi Sir,
Thanks for your effort. I have doubt in this. I understand the service principal is help to authenticate with Azure. If suppose we are running application that needs to access Azure resources and also it is hosting outside of Azure, that time only need service principal? and Is there any alternative way in azure like access key id and secret access key in AWS to access resource in AWS?
Thank you for your question! You're correct that a service principal is used to authenticate with Azure, especially when an application needs to access Azure resources.
If your application is hosted outside of Azure, using a service principal is a common approach to securely authenticate and access resources in Azure. However, if your application is running within Azure, you might consider using a Managed Identity instead, (new video is coming) which simplifies the process by automatically handling the identity management for you without needing to manage credentials like a service principal.
Regarding your comparison with AWS, the closest alternative would be Azure's Shared Access Signatures (SAS) or Application registration or API key or the use of Azure Active Directory (AD) for more fine-grained control. Each of these methods has its use cases, depending on the level of security and control you need.
Hope this helps.