Skip to content

chore: weekly message center posts refresh 2026-06-22 - #44

Open
soyalejolopez wants to merge 5 commits into
masterfrom
message-center/2026-06-22
Open

chore: weekly message center posts refresh 2026-06-22#44
soyalejolopez wants to merge 5 commits into
masterfrom
message-center/2026-06-22

Conversation

@soyalejolopez

Copy link
Copy Markdown
Owner

Automated weekly message center data update.

soyalejolopez and others added 5 commits May 27, 2026 14:40
Disable automatic publish during solution import so Copilot Studio validates the agent after bot variables and connection references are registered. Update the packaged solution to 1.2.11.0 and align setup guidance with the manual publish step.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Code Review

This pull request updates the message center data in index.html by adding a new post, updating the status of several existing posts to 'completed', and removing older entries. The review feedback correctly identifies a mismatch in the agent audience key ('researcherAnalyst' instead of 'firstParty') in the newly added post, which would prevent it from being displayed under the First-Party Agents tab, and provides a code suggestion to fix it.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.


// ─── Message Center Data ─────────────────────────────────────────
const messageCenterPosts = [
{ id: 'MC1396361', title: 'Microsoft 365 Copilot: Publish organization prompts to Copilot Chat', category: 'Stay Informed', severity: 'medium', datePublished: '2026-06-18', actionRequiredBy: null, status: 'active', services: ['Microsoft 365 Copilot Chat'], summary: 'Microsoft 365 Copilot now lets admins create and publish organization-specific prompts in Copilot Chat, guiding users with curated, relevant starting points. This feature, rolling out July 2026, enhances productivity, reflects organizational priorities, includes usage analytics, requires no license changes, and is enabled by default.', tags: ['new-feature', 'user-impact', 'admin-impact'], isHighImpact: false, agentAudience: ['researcherAnalyst', 'full', 'declarative', 'toolkit'] },

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

high

Mismatch in Agent Audience Key

There is a mismatch between the audience key used in the message center data ('researcherAnalyst') and the key used in the React component's state/configuration ('firstParty').

In index.html:

  • The state defaults to 'firstParty' (line 198).
  • The agentTypes configuration defines the key as firstParty (line 239).
  • The filtering logic (line 759) checks post.agentAudience.includes(selectedAgentKeyForContent).

Because of this, any post with 'researcherAnalyst' in its agentAudience will never be displayed under the First-Party Agents tab.

To resolve this permanently, please update the generator script scripts/update-message-center.js to map/output 'firstParty' instead of 'researcherAnalyst'. For this PR, you can manually update this entry as shown in the suggestion.

Suggested change
{ id: 'MC1396361', title: 'Microsoft 365 Copilot: Publish organization prompts to Copilot Chat', category: 'Stay Informed', severity: 'medium', datePublished: '2026-06-18', actionRequiredBy: null, status: 'active', services: ['Microsoft 365 Copilot Chat'], summary: 'Microsoft 365 Copilot now lets admins create and publish organization-specific prompts in Copilot Chat, guiding users with curated, relevant starting points. This feature, rolling out July 2026, enhances productivity, reflects organizational priorities, includes usage analytics, requires no license changes, and is enabled by default.', tags: ['new-feature', 'user-impact', 'admin-impact'], isHighImpact: false, agentAudience: ['researcherAnalyst', 'full', 'declarative', 'toolkit'] },
{ id: 'MC1396361', title: 'Microsoft 365 Copilot: Publish organization prompts to Copilot Chat', category: 'Stay Informed', severity: 'medium', datePublished: '2026-06-18', actionRequiredBy: null, status: 'active', services: ['Microsoft 365 Copilot Chat'], summary: 'Microsoft 365 Copilot now lets admins create and publish organization-specific prompts in Copilot Chat, guiding users with curated, relevant starting points. This feature, rolling out July 2026, enhances productivity, reflects organizational priorities, includes usage analytics, requires no license changes, and is enabled by default.', tags: ['new-feature', 'user-impact', 'admin-impact'], isHighImpact: false, agentAudience: ['firstParty', 'full', 'declarative', 'toolkit'] },

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant