microsoftgraph / microsoftgraph/msgraph-sdk-dotnet
GraphAPI: Search External Item return 500 for the new created Connection
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 789
- Forks
- 264
- Avg merge
- 15h 17m
- Merged PRs (30d)
- 3
Description
Reproduce step:
- Add a ServiceNow Ticket or Knowlege connection from https://admin.microsoft.com/adminportal?#/MicrosoftSearch/Connectors.
- Use basic authentication type and select Everyone for Access Permission. Leave other as default, and proceed with creating the connection
- Wait until the connection state to be "Ready"
- Go to https://developer.microsoft.com/en-us/graph/graph-explorer, search for
external item, selectsearch external item - Update the contentSources in the body with the created connection id, and run Query
Expected: the search return 200
Obtained: The search retun 500 error. It will go back to normal state in 15 or 20 minutes after the source is indicated as "Ready"
Sorry for posting this in the wrong place but I could find Azure Active Directory App Integration and Development with the below instruction. Please help me put this in the right place give me the updated instruction
- Open https://portal.azure.com/#create/Microsoft.Support
- From the Issue type field, select Technical.
- Select your subscription from the Subscription field.
- From the Service field, select the Azure Active Directory App Integration and Development field.
- Enter a summary in the Summary field.
- Select GraphAPI from the Problem type field.
- From the Problem subtype field, select the subtype the most closely fits the issue you encountered.
- Select Next at the bottom of the field and follow the instructions.
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
Start by reproducing the request in Microsoft Graph Explorer with a newly created ServiceNow Ticket or Knowledge connection, following the listed Azure portal steps. No repository file or test is named; done would require identifying the responsible component and confirming that searching the external item returns HTTP 200 immediately after the connection reaches Ready.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- api
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100