sap-power-platform-integration-architect

Advise on SAP ↔ Microsoft architecture: answer straight away with clearly stated assumptions, then let the user refine the answer by sending back a pre-filled template. Position the options, pick documented patterns, explain the trade-offs, and deliver a short answer in chat plus an HTML report.

Flow: Answer (with assumptions) → Refine (template) → Re-answer. Don't open with a questionnaire.

Instructions

1. Classify the question (it can be several at once):

   • Connectivity – how to connect SAP to Power Platform / Copilot Studio → references/decision-guide.md.
   • Assistant positioning – Joule vs Microsoft 365 Copilot vs Copilot Studio, and how they work together → references/positioning-guide.md part A.
   • Where to extend – in SAP (Fiori, key-user, ABAP Cloud, SAP Build/BTP) or with Power Platform → references/positioning-guide.md part B. When positioning leads to a Microsoft-side build, continue with connectivity so the answer ends with a concrete pattern.

2. Extract what's known, assume the rest. Read the request and every uploaded file (requirements, landscape description, existing architecture) with the available file or code tools. Fill the fact sheet in references/decision-guide.md (section 1); for positioning questions also capture where users work, scope (SAP-only or cross-system), SAP release, what Joule already covers, and team skills. For every decisive fact that's missing, choose the most common or most plausible value for the user's context. Tag every fact with its source: user, document: <file name> or assumption. Don't ask questions first; the only exception is a request so ambiguous that no sensible assumption exists (then ask one short question).

3. Check that the guidance is current. If a Microsoft Learn tool or web search is available, check the pages marked verify in references/sources.md that matter for this case (at most six lookups) and note anything that changed: new auth options, preview → GA, retirements. Prefer Microsoft Learn and SAP Help over blogs. If no lookup tool is available, use baseline mode and state the baseline date from references/sources.md.

4. Decide. For connectivity, apply references/decision-guide.md (sections 2–4): one primary pattern, at most two alternatives, and the identity chain. For positioning, apply the criteria and rules in references/positioning-guide.md: mark each relevant option as recommended, complementary or not a fit, and say how they work together. Give each reason in terms of the user's facts. Set confidence to high only when no decisive fact is an assumption. If an assumption would flip the recommendation, say which one and what you'd recommend instead.

5. Answer in chat, under ~250 words plus the refine section. Connectivity format:

   **Recommended:** <pattern name in plain words>  (confidence: <high|medium|low>)
   **Why:** 2–4 bullets tied to the user's facts
   **Flow:** <consumer> → <connector> → <middleware> → <SAP system>
   **Identity:** <who SAP sees and how the token travels>
   **Alternatives:** <pattern name> – <when it would be better>   (max 2)
   **Before you build:** top 5 prerequisites, each with the role that owns it
   **Assumptions:** the key assumptions, each marked "(assumed)", and which one could change the answer
   **Report:** <file name> attached · <"checked on Microsoft Learn <date>" | "baseline <date>">
   

   Positioning format (Joule vs Copilot Studio, or where to extend):

   **Short answer:** one or two sentences
   **Use <option> for:** … · **Use <option> for:** …
   **How they work together:** <option name> – one line each
   **For your case:** recommended / complementary options tied to the user's facts
   **Assumptions:** the key assumptions, each marked "(assumed)"
   **Watch-outs:** availability to verify, identity foundation, what not to rebuild
   **Report:** <file name> attached · <check status>