-
Notifications
You must be signed in to change notification settings - Fork 398
Frist draft to update meeting artifacts #9465
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
Frist draft to update meeting artifacts #9465
Conversation
Learn Build status updates of commit a8620c6:
|
File | Status | Preview URL | Details |
---|---|---|---|
concepts/cloud-communications-online-meeting-artifacts.md | Details |
concepts/cloud-communications-online-meeting-artifacts.md
- Line 13, Column 1: [Warning: link-out-of-scope - See documentation]
File '../api-reference/v1.0/resources/meetingattendancereport.md' referenced by link '../api-reference/v1.0/resources/meetingattendancereport.md' will not be built because it is not included in build scope.
- Line 28, Column 53: [Warning: link-out-of-scope - See documentation]
File '../api-reference/v1.0/api/meetingattendancereport-get.md' referenced by link '../api-reference/v1.0/api/meetingattendancereport-get.md#permissions' will not be built because it is not included in build scope.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
Learn Build status updates of commit f5120f4:
|
File | Status | Preview URL | Details |
---|---|---|---|
concepts/cloud-communications-online-meeting-artifacts.md | Details |
concepts/cloud-communications-online-meeting-artifacts.md
- Line 12, Column 89: [Warning: link-out-of-scope - See documentation]
File '../api-reference/v1.0/resources/meetingattendancereport.md' referenced by link '../api-reference/v1.0/resources/meetingattendancereport.md' will not be built because it is not included in build scope.
- Line 27, Column 53: [Warning: link-out-of-scope - See documentation]
File '../api-reference/v1.0/api/meetingattendancereport-get.md' referenced by link '../api-reference/v1.0/api/meetingattendancereport-get.md#permissions' will not be built because it is not included in build scope.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
Learn Build status updates of commit 1f5ec7f:
|
File | Status | Preview URL | Details |
---|---|---|---|
concepts/cloud-communications-online-meeting-artifacts.md | Details |
concepts/cloud-communications-online-meeting-artifacts.md
- Line 12, Column 123: [Warning: link-out-of-scope - See documentation]
File '../api-reference/v1.0/resources/meetingattendancereport.md' referenced by link '../api-reference/v1.0/resources/meetingattendancereport.md' will not be built because it is not included in build scope.
- Line 27, Column 53: [Warning: link-out-of-scope - See documentation]
File '../api-reference/v1.0/api/meetingattendancereport-get.md' referenced by link '../api-reference/v1.0/api/meetingattendancereport-get.md#permissions' will not be built because it is not included in build scope.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
#sign-off |
Learn Build status updates of commit a1f325a:
|
File | Status | Preview URL | Details |
---|---|---|---|
concepts/cloud-communications-online-meeting-artifacts.md | Details |
concepts/cloud-communications-online-meeting-artifacts.md
- Line 12, Column 120: [Warning: link-out-of-scope - See documentation]
File '../api-reference/v1.0/resources/meetingattendancereport.md' referenced by link '../api-reference/v1.0/resources/meetingattendancereport.md' will not be built because it is not included in build scope.
- Line 26, Column 62: [Warning: link-out-of-scope - See documentation]
File '../api-reference/v1.0/api/meetingattendancereport-get.md' referenced by link '../api-reference/v1.0/api/meetingattendancereport-get.md#permissions' will not be built because it is not included in build scope.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
Learn Build status updates of commit 834d4ec: 💡 Validation status: suggestions
concepts/cloud-communications-online-meeting-artifacts.md
For more details, please refer to the build report. Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them. For any questions, please:
|
The content is outdated and confused security reviewers from Eli Lilly and destroys trust with Microsoft.
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.