microsoft / microsoft/AdaptiveCards
Debugger add-in returns "failed" due to failed REST API calls
Open
Nobody has claimed this yet.
Area-Renderers
Bug
- Dominant language
- C#
- Stars
- 2k
- Forks
- 595
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 1
Description
Target Platforms
Other
SDK Version
N/A
Application Name
Microsoft Outlook
Problem Description
The OAM debugger add-in no longer works on most M365 tenants.
It returns a "failed" message only:
Quickly glossing over it, it seems to be leveraging the Outlook REST API, so it fails on any M365 tenant where legacy Exchange tokens are disabled.
Screenshots
No response
Card JSON
<script type=”application/adaptivecard+json”>
{
"$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
"type": "AdaptiveCard",
"version": "1.0",
"originator": "@{REDACTED}",
"body": [
{
"type": "Container",
"items": [
{
"type": "TextBlock",
"text": "Hello, World!",
"weight": "bolder",
"wrap": true
}
]
}
]
}
</script>
Sample Code Language
No response
Sample Code
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are identified in the issue. Reproduce the debugger add-in failure in a Microsoft 365 tenant with legacy Exchange tokens disabled, then trace the REST API calls that return errors. Done means the add-in no longer reports only "failed" on affected tenants.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100