Skip to content

Update RecoverDeletedItemsEnabled parameter applicability#13614

Open
TomonoriAbe wants to merge 2 commits into
MicrosoftDocs:mainfrom
TomonoriAbe:patch-7
Open

Update RecoverDeletedItemsEnabled parameter applicability#13614
TomonoriAbe wants to merge 2 commits into
MicrosoftDocs:mainfrom
TomonoriAbe:patch-7

Conversation

@TomonoriAbe
Copy link
Copy Markdown
Contributor

No description provided.

@learn-build-service-prod
Copy link
Copy Markdown
Contributor

Learn Build status updates of commit ac80268:

❌ Validation status: errors

Please follow instructions here which may help to resolve issue.

File Status Preview URL Details
inkcanvas/docfx.json ❌Error Details

inkcanvas/docfx.json

  • Line 8, Column 33: [Error: moniker-range-invalid] Invalid moniker range: 'samples-v1.0'. Moniker 'samples-v1.0' is not defined.
  • Line 14, Column 33: [Error: moniker-range-invalid] Invalid moniker range: 'samples-v1.0'. Moniker 'samples-v1.0' is not defined.
  • Line 20, Column 36: [Error: moniker-range-invalid] Invalid moniker range: 'testmoniker-1.0'. Moniker 'testmoniker-1.0' is not defined.
  • Line 20, Column 36: [Error: moniker-range-invalid] Invalid moniker range: 'testmoniker-1.0'. Moniker 'testmoniker-1.0' is not defined.
  • Line 1, Column 1: [Suggestion: uhf-header-id-missing - See documentation] uhfHeaderId should not be null; specify the uhfHeaderId in global metadata of docfx.json file.

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.

@github-actions
Copy link
Copy Markdown

@Cloud-Writer @lusassl-msft @mukeshHCW
You've been added as a reviewer to this pull request because you're listed as a Content Lead for the product area or feature covered by one or more articles in this PR.

Before this PR can be merged, a Content Lead needs to add the Sign off label to it. Only one of the listed reviewers needs to add the Sign off label. Before you sign off a PR, confirm the following:

  • The PR is not in draft state. When the changes in this PR are ready to be published, select the Ready to merge button at the bottom of the page.
  • Article content has been checked for technical accuracy.
  • There are no errors or warnings in build validation.
  • There are no severity 1 or 2 PoliCheck issues.
  • All required PR checks at the bottom of the PR are passing.

After you've confirmed the above, do the following to sign off:

  1. Select the gear next to Labels.
  2. Select Sign off from the label list.
  3. Click away from the label list.

image

After you've signed off, our operations (PubOps) team will review the PR for issues that may impact formatting and the customer experience. If any changes are needed, they will return
the PR to the submitter with required changes. After they've completed those changes, you need to sign off again.

When the PR passes PubOps review, they'll merge the PR. If the PR is merged into the main branch, changes will go live within the next couple hours.

If you think you were incorrectly added as a reviewer, have questions about this process, or need help signing off on this PR, post a message to https://aka.ms/tcphelp.

@learn-build-service-prod
Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 8f60e08:

✅ Validation status: passed

File Status Preview URL Details
exchange/exchange-ps/ExchangePowerShell/Set-OwaMailboxPolicy.md ✅Succeeded View (exchange-ps)

For more details, please refer to the build report.

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.

3 participants