Hello Sarah Elepo,
I understand you are seeing a 403 error when entering a damaged gift card code with the Code Assist bot, and you’d like to determine whether the issue is systemic or local to your environment.
There was an incident due to large number of requests but that has been mitigated now.
Here are additional details and next steps to help isolate future scenarios:
- Input Validation or Moderation Rules
- The bot may have content filters or rules rejecting certain patterns (such as “damaged code” or sensitive keywords).
- If there’s a moderation service in the bot stack, it might treat gift card/gift code-like strings as restricted content (often for fraud prevention).
- Check Account / Tenant Permissions & Bot Settings
- If this bot is tied to certain throttled or limited tiers, error 403 could also be triggered by exceeding some policy rule or quota.
- Confirm that your user account has the proper permissions / is not blocked / has not had its roles changed.
- Service-Side Status
- Verify whether there are known outages or incidents reported for Azure Bot Service (or Code Assist in particular). Sometimes service issues cause entire features to return forbidden or unavailable.
- Replicate From Different Contexts
- Try running the same input from a different user account or different channel (if the bot works via web, mobile, etc.).
- If embed or external client, check whether the bot behaves differently inside Azure portal vs external integration.
For reference: https://azure.status.microsoft/en-us/status
Please accept the answer and upvote, for other community member remediation.
Thank you for helping Q&A community. 😊