TWL-KB-048 · Viva Engage · Everyday user

Community content is unavailable

Confirm the community and the intended audience.

Applies to: Viva Engage.

Revision 5 · 18 November 2026 · General first-line guidance. Wording varies by version; a symptom is not a confirmed diagnosis.

Access / unavailable content (wording varies). Confirm the community and the intended audience.
Original explainer illustration, not a product screenshot. Select it to enlarge. All information is also in the text.

What does the message mean?

Some rows describe a visible symptom rather than an exact message. Wording marked “varies” may differ on your screen.

What you seeWhat it may indicateWhat to check
Access / unavailable content (wording varies)The community, the content link or your account may not have access in this context.Confirm the community and the intended audience.
No message at allProblems can happen without any message. A blank screen or a missing control is still useful evidence.Record the visible behaviour, the time and who is affected. Do not guess a code.
First checks: Confirm the link; Check the account; Record the message; Ask the community owner
Original explainer illustration, not a product screenshot. Select it to enlarge. All information is also in the text.

Step-by-step checks

Work in order and stop when it is resolved. If your screen differs, note what is different and ask IT or the owner.

  1. Confirm the link

    Do this
    Ask the community owner to verify the content link.
    What you should see
    The link is current.
    Then what?
    If this explains what you see, record it and continue only if the next check still applies.
  2. Check the account

    Do this
    Use the intended organisational account.
    What you should see
    The account is right.
    Then what?
    Record the result without changing settings. Stop if work, data or security could be affected.
  3. Record the message

    Do this
    Tell missing content apart from an access restriction without copying private posts.
    What you should see
    You know which it is.
    Then what?
    Use only the approved action described here. If it does not match your screen, stop and ask IT.
  4. Ask the community owner

    Do this
    Use the owner or IT route. Do not repost private content publicly.
    What you should see
    The owner can help.
    Then what?
    If unresolved, contact IT or the owner with sanitised evidence. Do not repeat actions that could duplicate data.

When to stop and contact IT or the owner

What to put in your support request

The app and version if visible, your device, the time, the exact message, who is affected, and the checks you tried with what you saw. Remove names, addresses and confidential content from screenshots. Never send passwords or MFA codes.

Microsoft reference

Microsoft documentation for this topic (opens a new tab). Some links are product hubs. Official pages may include advanced steps; ask IT before applying them on a managed device.

Related guides

The Workflow Lab is independent of Microsoft and is not your employer’s service desk.