Azure Communication Services (ACS) provides a managed platform and communication APIs to build real-time voice, video, SMS, and Chat functionality to your solution at scale. In the previous post – Azure Communication Services – Building an experimental messaging solution, we have learned how to leverage the Azure Portal to provide ACS and explore some of the features by building one simple messaging application. In this post, let us examine how we can leverage the existing Azure Communication Services (ACS) as a Microsoft Power Automate Connector to send SMS using a phone number.
Azure Communication Services(ACS) provides a managed platform and communication APIs to build real-time voice, video, SMS, and Chat functionality to your solution at scale. We can make our custom enterprise solution across any device or any platform. Azure Communication Services uses underlying reliable and secure infrastructure that powers by Microsoft Teams. So we don’t need to worry about the platform’s reliability and scalability while considering building a solution using ACS. When it comes to security and compliance, all the communications between ACS Platform and solutions are encrypted to meet privacy and compliance guidelines such as HIPAA and GDPR. Azure Communication Services also provides comprehensive supports of Developer’s SDKs and APIs for common platforms and languages, including Web, .NET, JavaScript, pythons, and devices like iOS and Android.
Azure Cosmos DB is one of the most impressive platform service that is schema-agnostic, fully managed, globally distributed, and multi-model database. Azure Cosmos DB offers scale, low-latency, and high throughput with API’s support of SQL, MongoDB, Cassandra, and tables. It also provides global distribution, which means you can scale and distribute it across different Azure regions. While designing a solution for the cloud, one of the critical considerations is how to make it cost-effective. In this post, let us quickly examine what offers Azure Cosmos DB provides to build a cost-effective solution.
Daily .NET Tips is aiming to share valuable coding tips and tricks for Developers. This site exclusively intends for sharing Tips and Tricks, useful Code Snippet, new features, which developers use in their regular development work. In this post, I am quickly listing down all the tips shared over the month of june 2020.
Let’s continue with the previous post on 10 Azure services that every .NET Developers, Consultant, and Architects should know and learn it well. Let us quickly recap what we talked about in the previous post before we move forward. Speed and agility are the keys for any organization to succeed. Moving to cloud services is no more an option – It’s compulsory and a smart move. Cloud Services provide lower cost, higher security, a global footprint, and increase productivity with powerful tools and frameworks. If you are working on Microsoft Platform, no matter what role you are performing – Development Engineer, Engineer in Test, Engineering Consultant, or Architect – understanding of fundamentals of cloud computing and usages are keys.
Speed and agility are the keys to any organization to success. Moving to cloud services is no more an option – It’s compulsory and a smart move. Cloud services bring speed and agility by enabling a rapid pace in development, managing services, and deploying the application on a massive scale over a global network. Cloud Services provide lower cost, higher security, a global footprint, and increase productivity with powerful tools and frameworks. Microsoft Azure, the leading cloud platform provider, evolve in magnitude over the past few years and provides a wide range of services for almost every scenario you need for your business.
Azure Bot Service is the Bot-Service powered by the Microsoft Bot Framework running on Microsoft Azure platform. It provides the integral components for developing bots, Bot Builder SDK and the Bot Framework for communicating bots to channels.
Most the people who were in the TechEd 2012 India would have witnessed the cool demo by me and Jebarson made on the opening Keynotes of the event. And now we would like to share how this solution was developed so that you can also build your own.
Background
Before we could pitch in, let me give a little background on how we decided to build this on our garage. Developer Conference 2011 on Hyderabad was scheduled on October 2011 and myself and Jebarson were looking forward to show something cool on our own interested areas. Jebarson was looking out for something on Windows Azure and Windows Phone while myself was fiddling around Kinect. Ran out of ideas we both met together and thought of integrating everything and that is when we came up with the idea of building our own home security. We started building this application as early as September 2011. And by now, we have already revised the application more than 5 times due to newer SDK release and also due to the addition of newer components.