Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Unable To Find Target Address" when creating community in an application registration context using [POST]/employeeExperience/communities #2697

Closed
vincent-preuvot opened this issue Oct 3, 2024 · 4 comments
Labels
Status: No recent activity status:waiting-for-author-feedback Issue that we've responded but needs author feedback to close type:bug A broken experience

Comments

@vincent-preuvot
Copy link

Describe the bug

I've performed some test on the recently released GRAPH endpoint /employeeExperience/communities.

Communities creations using delegated or direct account permissions are working fine (tested via GRAPH explorer) :

Capture d'écran 2024-10-02 075738

But when i try to create a community using an authentication done via Application Registration + Certificate, i have the following error :

Capture d'écran 2024-10-02 075949

Here is the full code of the method :

Capture d'écran 2024-10-03 141134

Remark : i'm not using the last version of the C# graph library since i have in my project a dependency to PnP.PowerShell wich is not compatible with the 5.x versions of the graph library (even if PnP.PowerShell should support versions of graph >= 3.33). That's why i do "raw" http requests to this graph endpoint.

Expected behavior

The community should be created with the specified owner

How to reproduce

Call the [POST]/employeeExperience/communities GRAPH API to create a community with specific owner(s) using a context/authentication done through Application Registration.

SDK Version

3.33.0 (also tested with last version)

Latest version known to work for scenario above?

No response

Known Workarounds

No response

Debug output

Click to expand log ```
</details>


### Configuration

_No response_

### Other information

_No response_
@vincent-preuvot vincent-preuvot added status:waiting-for-triage An issue that is yet to be reviewed or assigned type:bug A broken experience labels Oct 3, 2024
@andrueastman
Copy link
Member

Thanks for raising this @vincent-preuvot

To help narrow things down, with the example at the link below, are you able to capture the error information of the request with the latest version of the SDK?
https://learn.microsoft.com/en-us/graph/api/employeeexperience-post-communities?view=graph-rest-1.0&tabs=csharp#example-2-application-permissions

Are you able to capture the RequestId and ClientRequestId properties of the nested error object?
https://github.com/microsoftgraph/msgraph-sdk-dotnet/blob/main/docs/errors.md

@andrueastman andrueastman added status:waiting-for-author-feedback Issue that we've responded but needs author feedback to close and removed status:waiting-for-triage An issue that is yet to be reviewed or assigned labels Oct 9, 2024
@vincent-preuvot
Copy link
Author

Hi @andrueastman and thank you for your answer.

During my tests i tried with the latest SDK and i had the same issue.

I relaunched my code this morning and it works without changing anything ... do you know if there was a recent update on the GRAPH API endpoints ?

@microsoft-github-policy-service microsoft-github-policy-service bot added Needs: Attention 👋 and removed status:waiting-for-author-feedback Issue that we've responded but needs author feedback to close labels Oct 9, 2024
@andrueastman
Copy link
Member

I relaunched my code this morning and it works without changing anything ... do you know if there was a recent update on the GRAPH API endpoints ?

I can't say for sure TBH. I'm not sure if there's something that changed from the API side.

If its okay, we can close this one and you can re-open incase this happens/re-occurs?

@andrueastman andrueastman added status:waiting-for-author-feedback Issue that we've responded but needs author feedback to close and removed Needs: Attention 👋 labels Oct 9, 2024
Copy link
Contributor

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: No recent activity status:waiting-for-author-feedback Issue that we've responded but needs author feedback to close type:bug A broken experience
Projects
None yet
Development

No branches or pull requests

2 participants