-
Notifications
You must be signed in to change notification settings - Fork 320
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
Update best-practices-concept.md #9480
Conversation
Adding support boundaries for third-party apps as per CSS policy
Learn Build status updates of commit 9d89952: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
adding instructions for third-party app support as per CSS policy |
concepts/best-practices-concept.md
Outdated
@@ -160,3 +160,4 @@ To ensure reliability and facilitate support for your application: | |||
- Generate a unique GUID and send it on each Microsoft Graph REST request. This helps Microsoft investigate any errors more easily if you need to report an issue with Microsoft Graph. | |||
- On every request to Microsoft Graph, generate a unique GUID, send it in the `client-request-id` HTTP request header, and also log it in your application's logs. | |||
- Always log the `request-id` and `Date` from the HTTP response headers. These, together with the `client-request-id`, are required when reporting issues in [Microsoft Q&A](/answers/products/m365#microsoft-graph) or to Microsoft Support. | |||
- If you are using a third-party application, you will need to enagage the vendor with our support team in order to be able to investigate any issue in the third-party application. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- If you are using a third-party application, you will need to enagage the vendor with our support team in order to be able to investigate any issue in the third-party application. | |
- If you're using a third-party application, you need to engage with our support team to investigate the issue. |
@BassamMSFT , how do they engage with the support team? And, are you implying that there's a vendor that needs to engage with the support team? The text added wasn't quite clear; see if my suggested revision is accurate.
Hi Laura,
I’m from Graph API support team in Microsoft. We get too many cases where the customer is using a third-party application from a vendor where the application is using Graph API in the backend. But because the app is third-party then the customer can’t provide any request ids or any sample source code to investigate the Graph API issue. Those can only be obtained from the application developer’s side. i.e. the vendor.
So if a customer opens a support ticket with us, Microsoft, we need him to also have another support ticket with the vendor team and get an engineer from their end so that engineer can provide us with the Graph API request and app source code if required.
I’m not sure how to word it better in the public docs, but I will leave that to you 😊
Best regards.
Bassam Abd Elaziz
Support Escalation Engineer, Graph API Support
Modern Solutions & Support
+2 (02) 35393432
Working hours: Sunday-Thursday 9:00am – 6:00pm GMT+2
Manager: Daniela Maria Cochirleanu ***@***.******@***.***>
Can’t reach me? Call (888) get-help
[Image result for microsoft logo]
From: Laura Graham ***@***.***>
Sent: Wednesday, December 11, 2024 4:36 AM
To: microsoftgraph/microsoft-graph-docs-contrib ***@***.***>
Cc: Bassam Abd Elaziz ***@***.***>; Mention ***@***.***>
Subject: Re: [microsoftgraph/microsoft-graph-docs-contrib] Update best-practices-concept.md (PR #9480)
@Lauragra commented on this pull request.
________________________________
In concepts/best-practices-concept.md<#9480 (comment)>:
@@ -160,3 +160,4 @@ To ensure reliability and facilitate support for your application:
- Generate a unique GUID and send it on each Microsoft Graph REST request. This helps Microsoft investigate any errors more easily if you need to report an issue with Microsoft Graph.
- On every request to Microsoft Graph, generate a unique GUID, send it in the `client-request-id` HTTP request header, and also log it in your application's logs.
- Always log the `request-id` and `Date` from the HTTP response headers. These, together with the `client-request-id`, are required when reporting issues in [Microsoft Q&A](/answers/products/m365#microsoft-graph) or to Microsoft Support.
+ - If you are using a third-party application, you will need to enagage the vendor with our support team in order to be able to investigate any issue in the third-party application.
⬇️ Suggested change
- - If you are using a third-party application, you will need to enagage the vendor with our support team in order to be able to investigate any issue in the third-party application.
+ - If you're using a third-party application, you need to engage with our support team to investigate the issue.
@BassamMSFT<https://github.com/BassamMSFT> , how do they engage with the support team? And, are you implying that there's a vendor that needs to engage with the support team? The text added wasn't quite clear; see if my suggested revision is accurate.
—
Reply to this email directly, view it on GitHub<#9480 (review)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AZVBKVXMNALU6XXD2IP7ACT2E6QJJAVCNFSM6AAAAABTK2JEQGVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDIOJUGE3DANBXG4>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
Learn Build status updates of commit 7fc46f1: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
Adding support boundaries for third-party apps as per CSS policy
Important
Required for API changes:
Add other supporting information, such as a description of the PR changes:
ADD INFORMATION HERE
Important
The following guidance is for Microsoft employees only. Community contributors can ignore this message; our content team will manage the status.
After you've created your PR, expand this section for tips and additional instructions.
#feedback-addressed
to the pull request.For more information, see the Content review process summary.