--- title: "Connect Sorry to Azure Communication Services Identity - APIANT.ai" description: "When \"New notice\" fires in Sorry, your agent runs \"Issue Access Token\" in Azure Communication Services Identity." canonical: "https://apiant.ai/connect/sorry-to-azure-communication-services-identity" --- # Connect Sorry to Azure Communication Services Identity When **New notice** fires in [Sorry](https://apiant.ai/connections/sorry), your agent runs **Issue Access Token** in [Azure Communication Services Identity](https://apiant.ai/connections/azure-communication-services-identity). Describe the whole flow and it is built, tested on every scenario and kept running. Sorry **1** trigger Sorry **16** actions Azure Communication Services Identity **4** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want Sorry and Azure Communication Services Identity to do together? Give your AI client this address. `https://mcp.apiant.ai` One connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser. ### Set it up in your client ### Claude Code Run this in the directory you want to work in. `claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai` Start Claude Code there, approve the server, and sign in in the browser page it opens. [Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code) ### Claude, web and desktop Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Cursor Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Zed Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Codex and the ChatGPT desktop app Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Any other MCP client Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) Example flows ## What Sorry can start in Azure Communication Services Identity - When **New notice** in Sorry then **Issue Access Token** in Azure Communication Services Identity - When **New notice** in Sorry then **Create User** in Azure Communication Services Identity Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships. Everything your agent can do with Sorry and Azure Communication Services Identity ## Triggers and actions 1 trigger · 20 actions - Trigger **New notice** Triggers when a new notice (incident, maintenance or general announcement) is created on the selected Sorry status page. - Action **Add component** Creates a new component on a Sorry status page, optionally nested under a parent component. - Action **Add notice** Creates a new incident, maintenance or general notice on a Sorry status page, optionally linking affected components and publishing it to subscribers. - Action **Add notice update** Posts a new update on an existing notice on a Sorry status page, optionally publishing it to your configured integrations. - Action **Add subscriber** Adds an email or SMS subscriber to a status page, optionally limited to specific components, so they receive status notices. - Action **Delete notice** Deletes a notice (incident, maintenance or general) from a Sorry status page. - Action **Delete subscriber** Permanently removes a subscriber from a status page. - Action **Get notice** Returns a single notice from a status page, including its type, state, subject, synopsis and link. - Action **Get status page** Returns a single Sorry status page with its name, state, timezone, support details and notification settings, optionally including related brand, components, notices and more. - Action **List components** Returns all components (the services or infrastructure elements) shown on a Sorry status page, with their current state. - Action **List notices** Returns the notices (incidents, maintenance and general notices) posted on a Sorry status page, optionally filtered by type, state, subject or creation date. - Action **List notice updates** Returns all updates posted on a notice on one of your Sorry status pages, optionally filtered by creation date or content. - Action **List status pages** Returns all status pages in your Sorry account, optionally filtered by name or creation date. - Action **List subscribers** Returns the subscribers on a status page, optionally only those who receive notices for a specific component. - Action **Update component** Updates a component on a Sorry status page, such as its name, description, position or parent component. - Action **Update notice** Updates an existing notice on a Sorry status page — change its subject or state, add a comment, set affected components or reschedule planned maintenance. - Action **Update status page** Updates a status page's settings, such as its name, timezone, support contact details, search visibility and language. - Action **Create User** Creates a Communication Services user identity and, optionally, issues it an access token for chat or calling. - Action **Delete User** Deletes a Communication Services user identity and revokes all of its access tokens. - Action **Issue Access Token** Issues a new access token for a Communication Services user, for use with chat or calling. - Action **Revoke Access Tokens** Revokes every access token issued to a Communication Services user, so they must be issued a new one. ## Each app on its own - [ **Sorry** Status page and incident communication platform for notifying customers about downtime.](https://apiant.ai/connections/sorry) - [ **Azure Communication Services Identity** REST API for creating Azure Communication Services user identities and issuing scoped access tokens for chat...](https://apiant.ai/connections/azure-communication-services-identity) Reviews ## What our customers say ## More from Sorry - [ **Sorry to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/sorry-to-stripe) - [ **Sorry to Trello** Trello is a visual collaboration tool that organizes projects into boards, lists, and cards.](https://apiant.ai/connect/sorry-to-trello) - [ **Sorry to Zoom** Zoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...](https://apiant.ai/connect/sorry-to-zoom) - [ **Sorry to Twilio** Cloud communications platform for sending SMS/MMS messages, making and managing voice calls, and looking up...](https://apiant.ai/connect/sorry-to-twilio) - [ **Sorry to Typeform** Build and publish online forms, surveys, and quizzes with Typeform.](https://apiant.ai/connect/sorry-to-typeform) - [ **Sorry to Webflow** Webflow is a professional website builder and CMS for designing, building, and launching responsive...](https://apiant.ai/connect/sorry-to-webflow) ## More into Azure Communication Services Identity - [ **HubSpot to Azure Communication Services Identity** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-azure-communication-services-identity) - [ **Salesforce to Azure Communication Services Identity** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-azure-communication-services-identity) - [ **Slack to Azure Communication Services Identity** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-azure-communication-services-identity) - [ **Google Sheets to Azure Communication Services Identity** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-azure-communication-services-identity) - [ **Gmail to Azure Communication Services Identity** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-azure-communication-services-identity) - [ **Google Calendar to Azure Communication Services Identity** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-azure-communication-services-identity) Questions ## Sorry and Azure Communication Services Identity, answered ### ### What can start an automation from Sorry? Any of Sorry's 1 trigger in the catalog, including New notice. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Azure Communication Services Identity when something happens in Sorry? Any of Azure Communication Services Identity's 4 actions, including Create User, Issue Access Token, Revoke Access Tokens and Delete User. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Azure Communication Services Identity to Sorry? Azure Communication Services Identity has no triggers in the catalog today, so automations start in Sorry. If you need the other direction, ask: your agent reads Azure Communication Services Identity's API documentation and adds it. ### ### Do I have to build a connector for Sorry or Azure Communication Services Identity? No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running. ### ### Can my AI client use Sorry and Azure Communication Services Identity without building an automation? Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both. ### ### What happens when something fails? Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships. ### ### Is there a free plan? Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.