القائمة
Use when: building or debugging Office 365 Groups connector flows in a Power Apps Code App, including group listing, membership, events, or openGroupsHttpRequest.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when: building or debugging Power Platform for Admins V2 connector operations in a Power Apps Code App, including environments, backups, disaster recovery, environment groups, governance policies, capacity, billing, cloud flows, Copilot agents, Power Pages, or tenant administration.
Use when: performing an evidence-based security review of a Microsoft Power Apps Code App, especially checking external runtime sources, hard-coded passwords or secrets, security by obscurity, hard-coded access bypasses, DOM injection, and sensitive client-side data without reporting package, server, CSP-header, authentication-host, or infrastructure false positives owned by the Microsoft managed platform.
Start skill for new Code App project setup. Use this skill when starting a fresh app build or UI build so the agent confirms theme direction, offers mockups, and only then implements files.
Use when: building or debugging Microsoft Teams connector flows in a Power Apps Code App, including teams, channels, chats, mentions, tags, notifications, cards, meetings, transcripts, recordings, schedules, or the Teams HttpRequest helper.
Use when: adding or calling Power Automate cloud flows from a Power Apps Code App, including callFlow(...), generated flow services, or shared_logicflows connectionReferences.
Use when: building or debugging SharePoint list, attachment, library, or file flows in a Power Apps Code App, including list-id or environment-variable-based setup.
| name | office365-groups |
| description | Use when: building or debugging Office 365 Groups connector flows in a Power Apps Code App, including group listing, membership, events, or openGroupsHttpRequest. |
Do not use CLI PAC commands to get connecctor models or services,
use codeApp/dist/connectors/office365groups.js as the repo source of truth.
Always read the current power.config.json before editing it.
Ensure "id": "/providers/Microsoft.PowerApps/apis/shared_office365" exists.
"connectionReferences": {
"office365groups": {
"id": "/providers/Microsoft.PowerApps/apis/shared_office365groups",
"displayName": "Office 365 Groups",
"dataSources": [
"office365groups"
],
"authenticationType": null,
"sharedConnectionId": null,
"dataSets": {}
}
}
Rules for editing power.config.json:
sharedConnectionId, authenticationType, and other working connection metadata.Prefer the exported helper layer instead of wiring raw connector operations directly in app code.
callGroupsOperation(operationName, parameters)openGroupsHttpRequest(options)listMyGroups(options)listOwnedGroups(options)listGroups(options)listGroupMembers(groupId, options)addMemberToGroup(userUpn, groupId)removeMemberFromGroup(userUpn, groupId)createGroupEvent(groupId, options)updateGroupEvent(eventId, options, groupId)deleteGroupEvent(eventId, groupId)listDeletedGroups()restoreDeletedGroup(groupId)listDeletedGroupsByOwner(userId)listMyGroups({ version: 1|2|3 }) routes to ListOwnedGroups, ListOwnedGroups_V2, or ListOwnedGroups_V3.listGroups(...) supports $filter, $top, skipToken, nextLink, and skip aliases.createGroupEvent(...) defaults to CreateCalendarEventV2.deleteGroupEvent(...) uses CalendarDeleteItem_V2.openGroupsHttpRequest(...) can target HttpRequest or HttpRequestV2 through version, useV2, or operationName.openGroupsHttpRequest(...) maps friendly inputs to connector fields:
uri -> Urimethod -> Methodbody -> BodycontentType -> ContentTypecustomHeaders[0..4] -> CustomHeader1..5Use this only when no helper exists for the action you need.
skipToken or nextLink, not a raw $skip query.openGroupsHttpRequest(...).