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

Update best-practices-concept.md #9480

Merged
merged 2 commits into from
Dec 13, 2024
Merged

Conversation

BassamMSFT
Copy link
Contributor

Adding support boundaries for third-party apps as per CSS policy

Important

Required for API changes:

  • Link to API.md file: ADD LINK HERE
  • Link to PR for public-facing schema changes (schema-Prod-beta/v1.0.csdl): ADD LINK HERE

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.
  • do not merge is the default PR status and is automatically added to all open PRs that don't have the ready to merge label.
  • Add the ready for content review label to start a review. Only PRs that have met the minimum requirements for content review and have this label are reviewed.
  • If your content reviewer requests changes, review the feedback and address accordingly as soon as possible to keep your pull request moving forward. After you address the feedback, remove the changes requested label, add the review feedback addressed label, and select the Re-request review icon next to the content reviewer's alias. If you can't add labels, add a comment with #feedback-addressed to the pull request.
  • After the content review is complete, your reviewer will add the content review complete label. When the updates in this PR are ready for external customers to use, replace the do not merge label with ready to merge and the PR will be merged within 24 working hours.
  • Pull requests that are inactive for more than 6 weeks will be automatically closed. Before that, you receive reminders at 2 weeks, 4 weeks, and 6 weeks. If you still need the PR, you can reopen or recreate the request.

For more information, see the Content review process summary.

Adding support boundaries for third-party apps as per CSS policy
Copy link

Learn Build status updates of commit 9d89952:

✅ Validation status: passed

File Status Preview URL Details
concepts/best-practices-concept.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@BassamMSFT
Copy link
Contributor Author

adding instructions for third-party app support as per CSS policy

@@ -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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 , 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.

@BassamMSFT
Copy link
Contributor Author

BassamMSFT commented Dec 11, 2024 via email

@Lauragra Lauragra merged commit 389690c into microsoftgraph:main Dec 13, 2024
6 of 7 checks passed
Copy link

Learn Build status updates of commit 7fc46f1:

✅ Validation status: passed

File Status Preview URL Details
concepts/best-practices-concept.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants