Engage with the Azure Community Services Ideas Board: Your Voice Matters
Innovation is not a solitary pursuit, and we recognize that some of the best ideas come from you, our Azure Communication Services community. By using our technology and identifying the limitations or feature gaps, you help us understand what we need to enhance to make Azure Communication Services a comprehensive platform for intelligent B2C communication for you and your team.
In short, your feedback helps drive our product development. To encourage ongoing feedback, we’re excited to highlight the Azure Communication Services – Community Ideas Board. This platform enables you to share insights and suggestions, which are invaluable in helping us prioritize new features.
We believe that hearing directly from our customers is essential. Like most popular community forums, the Azure Communication Services Community Ideas Board offers several key functions:
- Create a new topic that is important to you.
- Upvote topics to promote their visibility and prioritization.
- Add comments on existing posts to share your thoughts.
- Star a topic to follow it and receive notifications on further activity.
Although this Community Ideas board isn’t new to Azure Communication Services, we’re now committing to using it as a primary source of customer feedback to guide our prioritization and roadmap. The board is actively monitored by the Azure Communication Services team, and suggestions are communicated to the appropriate internal team members. Ideas with significant upvotes indicate crucial feature gaps that we’re eager to learn more about and address.
Getting involved is simple! Use your (digital) voice to make an impact. If there is a feature you believe is missing, create a topic and we will take notice. Or simply upvote an existing suggestion. Share your ideas and help shape the future of Azure Communication Services.
Thank you for being a part of the Azure Communication Services community. Some of our best ideas have come from conversations with our users, and we are grateful for your participation. See you on the Ideas Board!
Published on:
Learn moreRelated posts
Shrinking Azure Pipeline task extensions using esbuild
TL;DR We bundled an internal Azure Pipelines task extension into a single bundled JavaScript file using esbuild. The task package dropped from...
Building on Vercel’s eve + Azure Cosmos DB: An Agent That Remembers
Most “AI agent” demos forget everything the moment the process exits. That’s fine for a toy project, but useless for anythin...
Copilot Studio – Environment-level agent telemetry export to Azure Application Insights (Preview)
We are announcing the ability for administrators to export Copilot Studio agent telemetry at the environment level to Azure Application Insigh...
See our new Azure Cosmos DB Design Patterns
Design patterns are where good data modeling lives or dies. In a NoSQL database like Azure Cosmos DB, the difference between a schema that sca...
Need a different partition key in Azure Cosmos DB? Pick the right approach
Once you create a container, its partition key is fixed at creation, and you can’t change it in place. However, if your original key starts ca...
Azure SDK Release (June 2026)
Azure SDK releases every month. In this post, you'll find this month's highlights and release notes. The post Azure SDK Release (June 2026) ap...
Fundamentals of Azure DevOps with SQL projects
Building automated pipelines with your SQL database projects enables you to build a rich CI/CD ecosystem to ensure that your application is be...