Event banner
Event details
Hi esmond365!
Great question! It all depends on your use case 🙂 In general ACS is a platform offering (PaaS) and Teams is the full software/solution offering (SaaS).
If you want more customization, extensibility, and are not limited to only AAD identity, then ACS is a great option for you. If you just want to have a fully available solution ready to deploy and are using AAD, then Teams is the way to go.
As for leveraging other Microsoft offerings, we are investigating different ways we can plug into the larger Microsoft ecosystem to make a holistic experience for our customers. If you have feedback on other platforms to plug into (we are currently looking into low code platforms for example 🙂 ), we would love to hear your use cases/scenarios.
In general, ACS can be used in conjunction with most other Microsoft and Azure services since we are a set of SDKs/APIs that allow you to customize your product. You just might have to stitch a few things together on your side 😉
Does that answer your question?
- I encourage to document those known and proposed workflows to help contextualize the service as a utility layer for developers and practitioners. I like the low-code next step. I work in healthcare and am obviously biased to use-cases. To the HIPAA context raised by @ronnormon, I think theres solid value in a patient facing capacity for non-sensitive comms like SMS reminders etc.