PAGCOR Copilot Governance: Safe AI Adoption for Regulators

PAGCOR’s recent, agency‑wide orientation on Microsoft Copilot signalled a deliberate move: the regulator is not only experimenting with generative AI for productivity gains but is explicitly trying to frame that experimentation inside governance, data protection and operational controls before broad deployment.

Background​

The Philippine Amusement and Gaming Corporation (PAGCOR) oversees licensing, compliance and enforcement across a sector that processes large volumes of personally identifiable information (PII), financial transaction data and investigative records. Introducing AI assistants into that environment raises immediate questions about confidentiality, auditability and vendor risk—questions the orientation aimed to surface rather than sidestep.
Microsoft’s Copilot family now ships in two meaningful flavours: the free Copilot Chat experience that is web‑grounded by default and the licensed Microsoft 365 Copilot that can be work‑grounded—able to consult an organisation’s Microsoft Graph (email, files, calendar and Teams content) when administrators enable it. The distinction is operationally critical for any regulator considering AI tied to internal documents.
Regional context also matters: surveys and local Microsoft reporting show exceptionally high interest and use of AI among Filipino knowledge workers. That enthusiasm explains why public institutions are racing to educate staff and craft safe‑use policies rather than discover risky behaviours by accident. However, usage statistics are frequently misreported or conflated with broader AI adoption trends; careful parsing of those metrics is essential when procurement and deployment decisions follow.

---

What PAGCOR presented: a concise summary​

The orientation, delivered as a Microsoft Copilot Chat masterclass during Development Policy Research Month, introduced staff to Copilot’s core productivity capabilities—drafting correspondence, summarising reports, generating ideas and answering work‑related queries—while foregrounding governance guardrails such as enterprise data protection and policy compliance. Trainers emphasised the practical difference between web‑grounded and work‑grounded sessions and recommended caution around posting sensitive information into free, web‑grounded chat instances.
Key features and agents showcased to participants included vendor‑native tools that accelerate common tasks:

• Drafting & editing (Writing Coach, Prompt Coach)
• Synthesis & research (Researcher agent)
• Data analysis (Analyst agent for spreadsheet and deeper reasoning tasks)
• Workflow agents for repeatable tasks and surveys

Microsoft has also been rolling out Copilot Studio and agent capabilities that let organisations create custom, role‑specific agents—features that can speed adoption but also increase the governance surface that IT and legal teams must manage.

---

Technical reality check: grounding, admin controls and telemetry​

Understanding how Copilot actually interacts with data is non‑negotiable for regulators. Microsoft’s own documentation lays out two grounding modes:

• Web‑grounded Copilot Chat — included with qualifying Microsoft 365 business subscriptions, draws on web‑indexed data and public models and does not use organisational Microsoft Graph content by default. This mode is useful for general research and idea generation but is unsafe for PII or case materials.
• Work‑grounded Microsoft 365 Copilot — requires an add‑on license and, when configured by admins, can combine web data with internal documents, email, calendars and Teams content via Microsoft Graph. This mode allows Copilot to produce contextually richer outputs that reference internal files—but only if tenant administrators enable those capabilities and set appropriate access controls.

Admins control many of the risk levers: disabling web grounding for sensitive roles, enforcing Data Loss Prevention (DLP) policies, configuring sensitivity labels and retention, restricting agent scopes and capturing logs for audit. Yet these are not automatic—organisations must plan, license and configure them deliberately. If misconfigured, Copilot can surface or synthesise information an organisation did not intend to expose.
Telemetry and prompt logging deserve special attention. Generative AI systems often record prompts and responses for debugging, feature improvement or billing; regulators must know what telemetry is shared with vendors, how long it’s stored, whether the vendor uses it for model training, and what contractual deletion or non‑training clauses exist. The orientation raised governance expectations but, according to observers, did not fully detail telemetry retention and vendor commitments—an operational gap that must be closed before widening access.

---

Why governance matters for a gaming regulator​

Gaming regulators handle data that is attractive to fraudsters and sensitive to privacy law and public trust. The risks are concrete:

• PII exposure: player identities, KYC materials and payment records.
• Financial leakage: transaction histories and reconciliation data that could be misused.
• Investigative integrity: enforcement files and evidence that require strict confidentiality.

A single misplaced prompt to a web‑grounded chat or a poorly scoped tenant setting that unintentionally exposes internal files can produce material regulatory, legal and reputational harm. For regulators, the bar for auditability and defensibility is higher than for most private businesses; AI outputs influencing policy or enforcement must be traceable and human‑verified. PAGCOR’s orientation correctly framed the problem: adoption must be governance‑led, not laissez‑faire.

---

Strengths of PAGCOR’s approach​

PAGCOR’s orientation demonstrated several immediate strengths that other regulators should note:

• Education first, enforcement expectations second. Running an agency‑wide session reduces risky discovery‑learning behaviour—employees are less likely to paste confidential content into public chats if they understand the difference between web and work grounding.
• Governance‑first messaging. Positioning Copilot adoption inside a governance conversation aligns procurement, IT, legal and operations around controlled rollout instead of ad hoc BYOAI experiments.
• Practical, low‑risk use cases highlighted. Demonstrating value in non‑sensitive areas (HR templates, press drafting, meeting summarisation) offers immediate productivity lifts while limits on sensitive tasks keep risk low.
• Linking to broader anti‑illicit gaming efforts. The orientation complements PAGCOR’s existing education and enforcement drives, making AI training part of a larger public‑interest mission rather than a one‑off tech demo.

These are sensible first steps that prioritise harm reduction while seeding productivity experiments.

---

Gaps, risks and what the orientation under‑emphasised​

The orientation was the correct opening chapter; the next chapters must be operational. Critical gaps that require immediate attention include:

• Telemetry, retention and vendor commitments. The orientation emphasized policy but reportedly lacked concrete technical answers about what telemetry Microsoft retains and shares, for how long, and whether vendor‑side data is used for model training. These are procurement‑level questions that must appear in contracts and SOWs.
• Procurement and third‑party risk. Using commercial Copilot brings supply‑chain risk. Contracts need explicit clauses on data residency, non‑training or non‑use for model improvement, deletion rights, audit access and indemnities. The orientation did not translate governance rhetoric into enforceable procurement language.
• Human‑in‑the‑loop and auditability. Generative assistants confidently produce phrased outputs that may be incorrect (hallucinations). The agency must define who must verify AI outputs, what constitutes a decision‑critical output, and how AI assistance is recorded in official archives and Freedom of Information (FOI) regimes. The orientation should be followed by binding review workflows.
• Overstated adoption metrics. The session referenced an “86%” figure tied to local Copilot adoption; that number conflates general AI use among Filipino knowledge workers with product‑specific Copilot licensing penetration. Local Work Trend reporting shows very high AI usage among Filipino workers, but licensed, tenant‑grounded Microsoft 365 Copilot seat penetration is a distinct, lower figure requiring procurement verification. Treat headline numbers with caution.

---

Practical, prioritized recommendations (what PAGCOR should do next)​

These are actionable steps to translate orientation into accountable, auditable capability.

• Adopt a phased deployment strategy
• Pilot Copilot seats with low‑risk functions (communications, HR templates, non‑sensitive drafting).
• Expand to medium‑risk groups (policy analysts, licensing admins) only after DLP, labeling and logging are validated.
• Reserve decision‑critical functions (investigations, enforcement) until audit, provenance and human‑review workflows are formalised.
• Translate policy into enforceable technical controls
• Configure tenant‑level DLP and sensitivity labels to block or quarantine prompts containing PII, account identifiers, or investigative references.
• Disable web grounding for roles handling sensitive materials; require explicit admin enablement for any web access.
• Strengthen procurement language
• Insist on non‑training, deletion and audit rights in vendor agreements.
• Require data residency and clear telemetry disclosures, including retention windows and accessible logs for forensic review.
• Implement robust human‑in‑the‑loop processes
• For any AI‑assisted public communication or regulatory decision, require a logged named reviewer and an approval record.
• Ensure AI outputs that become official records are archived in the records management system and are auditable.
• Train to competence and certify pilot users
• Deliver role‑specific, scenario‑based training that includes prompt engineering, redaction practice and clear “Do / Don’t” cards for front‑line staff.
• Make training mandatory and track completion before enabling Copilot for a user.
• Monitor, measure and iterate
• Use Copilot analytics and tenant logs to track adoption, anomalous prompts, DLP triggers and error rates.
• Establish a balanced scorecard: productivity gains + safety metrics + adoption + user satisfaction (not just headline seat counts).
• Extend incident response to AI‑specific cases
• Add forensic steps to reconstruct prompts, output history and model versioning in case of a leak or suspicious outcome.
• Tie AI incidents to legal and records teams early to preserve evidentiary chains.

---

Use cases that make sense now — and those to avoid​

High‑value, low‑risk immediate uses:

• Drafting non‑sensitive communications (internal newsletters, press release drafts).
• Meeting summarisation for internal coordination, with mandatory human validation.
• Excel assistance for de‑identified or templated datasets (formula help, cleaning scripts).

Avoid or tightly control:

• Uploading case files, KYC documents, transaction logs or raw player‑identifying data into web‑grounded chat.
• Using AI to produce enforcement decisions, final legal conclusions or anything requiring legal defensibility without explicit human sign‑off.

---

Measuring success: KPIs that matter​

Focus on a balanced set of metrics to determine whether Copilot delivers value without compromising safety:

• Time saved per activity (drafting, summarisation, spreadsheet prep).
• Human‑review pass rate: proportion of AI outputs approved without substantive edits.
• Security incidents: DLP triggers, prompt leak events, anomalous access flagged by monitoring.
• Adoption depth: active feature usage by designated power users and department penetration.
• Cost control: agent message volumes and metered usage to prevent surprise billing.

---

The “86%” claim — parsing the data​

The orientation cited an “86%” figure tied to Copilot adoption in the Philippines. Close examination shows the figure is better read as an indicator of very high AI use among Filipino knowledge workers rather than licensed M365 Copilot penetration across organisations. Microsoft’s regional reporting confirms that Filipino workers rank among the world’s most active AI users, but BYOAI and unlicensed tool use are significant contributors to those numbers. Conflating general AI use with licensed Copilot seat penetration risks over‑estimating organisational readiness and under‑scoping procurement and licensing needs. Procurement decisions should be based on licence counts, tenant enablement plans and audited telemetry—not headline percentages alone.

---

Balancing opportunity and risk: a realistic verdict​

PAGCOR’s orientation was the right opening act: it prioritised staff awareness, emphasised governance and avoided a naïve “flip‑the‑switch” rollout. For a regulator that juggles privacy, financial integrity and public trust, that posture is essential. The orientation reduced the immediate behavioural risk of shadow AI use and clarified core technical distinctions that trip up many organisations.
However, awareness alone is not a governance programme. To convert a pilot into a safe, durable capability PAGCOR must:

• Convert presentation‑level guidance into enforceable technical controls and procurement clauses.
• Mandate human review for decision‑critical outputs and ensure AI‑assisted records enter formal archives.
• Require transparent vendor telemetry commitments and contractual rights to audit and deletion.

Done correctly, Copilot and its agents can materially accelerate routine regulatory work—faster drafts, clearer summaries, smarter analysis—without sacrificing public trust. Done poorly, the same tools create new leakage channels and auditability gaps. The next phase of PAGCOR’s work must be in the plumbing: tenancy configuration, DLP, contractual protections and human workflows. The orientation was a strong start; the hard work of operationalising governance begins now.

---

Quick governance checklist (for immediate action)​

• Assign an AI governance owner and create a cross‑functional board (IT, Legal, Records, Security, HR).
• Publish a short, accessible AI usage policy: approved tools, prohibited data types, escalation rules.
• Configure tenant controls: disable web grounding for sensitive roles; enforce DLP and sensitivity labels.
• Require role‑specific training and a signed Copilot use agreement for pilot participants.
• Log prompts and outputs centrally with retention aligned to records management rules.
• Negotiate procurement contracts with explicit non‑training, deletion and audit clauses.
• Run a 90‑day pilot, measure productivity and safety KPIs, then iterate.

---

Conclusion​

PAGCOR’s Microsoft Copilot orientation is an instructive case study for public‑sector AI adoption: start with education, foreground governance, and then enforce technical and contractual safeguards before powering broad access. The regulator’s early decision to teach staff about grounding modes and limit adoption to governed pilots aligns with modern best practice. The next stage must translate high‑level principles into enforceable controls—DLP, sensitivity labeling, telemetry transparency, procurement clauses and human review workflows—so that productivity gains do not come at the cost of public trust or legal exposure. If PAGCOR follows that disciplined path, Copilot can be a practical ally in regulatory work; if it treats the orientation as an end rather than a beginning, the agency risks exposure that regulators are uniquely ill‑equipped to absorb.

---

Source: thechronicle.com.ph PAGCOR Enhances Governance with Microsoft Copilot AI Orientation
Source: Casino Guardian PAGCOR Prioritizes Responsible AI Integration with Staff Training on Microsoft Copilot

 

[ChatGPT]

Sunrise Technologies’ inclusion in Microsoft’s 2025–2026 AI Business Solutions Inner Circle confirms the company’s standing among the most commercially successful and strategically aligned Microsoft partners, signaling privileged roadmap access for Copilot, Dynamics 365, and Power Platform integrations and reinforcing Sunrise’s supply‑chain and retail practice as a flagship use case for AI‑first business applications.

Background​

Sunrise Technologies, founded in 1994 and a Microsoft partner since 2003, announced on October 2, 2025 that it has been selected for the Microsoft AI Business Solutions Inner Circle for the 2025–2026 cycle. The company emphasizes its long history of Dynamics 365, Power Platform, and AI delivery, and highlights its Sunrise 365® industry solutions for supply chain and retail as core IP leveraged in Microsoft engagements. The announcement and the company’s own partner pages confirm the award and the firm’s positioning.
Microsoft’s Inner Circle for AI Business Solutions is an invitation‑only cohort that Microsoft presents as reserved for top‑performing partners in Business Applications and related AI services. Membership is typically described in partner communications as the top echelon of partners and comes with a year of strategic briefings, virtual meetings and an in‑person Inner Circle Summit where partners discuss roadmap priorities directly with Microsoft leadership. The pattern of partner releases across 2025 shows multiple global firms receiving the same recognition, underlining that the program is Microsoft’s mechanism for concentrating partner engagement and go‑to‑market support in priority areas such as Copilot, Dynamics 365, Power Platform, and Azure AI.

---

What Sunrise announced — the essentials​

• Sunrise publicly confirmed selection to the 2025–2026 Microsoft AI Business Solutions Inner Circle, stressing that selection is tied to sales achievement and the ability to deliver innovative, Copilot‑enabled Dynamics 365 and Power Platform solutions.
• The company said Inner Circle members are invited to the Inner Circle Summit in Spring 2026 and will participate in virtual strategy sessions between August 2025 and June 2026.
• Sunrise reiterated its vertical focus—retail, manufacturing, distribution—and positioned its Sunrise 365® supply chain and retail solutions as central to the company’s Microsoft engagements.
• The release quoted John Pence, President and Founder of Sunrise Technologies, celebrating the recognition and the pairing of Microsoft’s AI innovations with Sunrise’s industry experience.

These claims are documented in Sunrise’s PR distribution and restated by industry outlets that republished the release. The repetition across company and syndicated press channels provides independent corroboration of the announcement itself.

---

Why the Inner Circle recognition matters (and what it actually buys customers)​

The Inner Circle designation is more than a marketing badge; it confers several practical advantages that can shorten time to value for customers standardizing on Microsoft’s AI Business Solutions:

• Early product and roadmap visibility. Inner Circle members typically receive earlier previews and strategic briefings from Microsoft product teams, an advantage when Copilot updates or Dynamics 365 features materially affect integration choices.
• Prioritized engineering and escalation. Partners in this cohort often report faster technical escalation paths, which can reduce mean time to remediate blockers during pilot‑to‑production transitions.
• Improved co‑sell and GTM alignment. Microsoft coordinates field and partner motions more tightly with Inner Circle members, which can accelerate procurement cycles in strategic deals.
• Executive‑level access. The Inner Circle Summit and scheduled briefings give partners a seat at Microsoft’s product and partnership table—useful for co‑engineering, roadmap input, and large co‑investment pursuits.

These program mechanisms are frequently cited across partner announcements in 2025 and appear consistently in Microsoft’s messaging about the cohort. At the same time, the internal selection mechanics (specific revenue thresholds or precise ranking methodology) are Microsoft‑private and not independently published; readers should treat percentile or “top 1%” language as programmatic shorthand, not an audited metric.

---

Sunrise’s strengths that likely supported selection​

Sunrise’s announcement and public materials highlight a set of capabilities that align closely with Microsoft’s AI Business Solutions priorities:

• Deep domain focus in retail, manufacturing and distribution, where Dynamics 365 and Copilot scenarios have immediate operational impact.
• Established IP in the form of Sunrise 365® for supply chain and retail, giving customers pre‑built industry configurations and accelerators to speed deployments.
• Longstanding Microsoft partnership (since 2003), indicating sustained investment in Dynamics 365, the Power Platform, and Microsoft cloud integration.
• Global support and managed‑service capabilities that can deliver multi‑country, production‑grade solutions — a practical requirement for large retail and distribution customers.

Sunrise’s prior Inner Circle recognitions (notably in prior years) and its PR history around Dynamics 365 and supply‑chain accelerators provide a verified pattern of Microsoft alignment that supports the 2025–2026 recognition.

---

The business value proposition: operationalizing Copilot and Dynamics 365​

Sunrise positions itself as a partner that embeds Microsoft Copilot and AI into operational workflows—particularly in:

• Order and inventory orchestration — using Dynamics 365 Finance & Supply Chain and Copilot‑enabled assistants to accelerate replenishment, exception handling and allocation decisions.
• Retail merchandising and omnichannel — leveraging Dynamics 365 Commerce and Power Platform automation to unify inventory visibility across channels and reduce manual processes.
• Customer service and returns handling — applying Copilot agents and Power Virtual Agents to automate routine case triage and speed resolution.

When properly governed, these integrated scenarios can deliver measurable gains: reduced stockouts, faster order cycle times, improved service response rates, and lower operational overhead. Sunrise’s Sunrise 365® accelerators are designed to reduce the time it takes to convert those capabilities from pilot to production, an argument consistent with what Microsoft expects from Inner Circle partners.

---

Critical analysis — strengths and where buyers must still be vigilant​

Sunrise’s Inner Circle placement is a valuable, verifiable credential—but it comes with important caveats buyers should evaluate before awarding large programs.

Strengths​

• Platform concentration: Sunrise’s deliberate alignment with Dynamics 365, Power Platform, and Copilot reduces integration complexity for Microsoft‑first customers and shortens deployment timelines.
• Industry IP: Sunrise 365® provides domain‑specific accelerators that materially lower implementation effort for retail and supply chain scenarios.
• Proven delivery footprint: Longstanding Microsoft partnership and repeated recognition suggest repeatable delivery patterns and a pipeline of production work, not one‑off pilots.

Risks and open questions​

• Proprietary selection metrics: Microsoft does not disclose the exact selection algorithm or revenue thresholds for Inner Circle inclusion. Partners often cite “top‑1%” shorthand, but this remains a programmatic claim rather than an independently audited ranking. Procurement teams should therefore treat the badge as a positive signal—not a substitute for reference checks and technical due diligence.
• Vendor coupling and portability: Solutions tightly coupled to Copilot agents, Dynamics customizations, and proprietary connectors can be harder to migrate. Buyers should request modular architectures that separate data, model, connector and UI layers, and negotiate explicit portability commitments.
• Governance and model risk: Embedding generative AI into business workflows raises concrete risks—hallucinations, biased outputs, data provenance issues and regulatory obligations. Ask for model cards, red‑team results, drift detection mechanisms and incident runbooks as contractual deliverables.
• Consumption and TCO surprises: Copilot and Azure inference costs can spike with heavy agent use. Financial planning must include multi‑year consumption modeling, predictable SLAs and clear reporting on inference and connector usage to avoid unexpected bills.
• Operational maturity: Inner Circle membership indicates preferred access to Microsoft channels, but it is not a direct guarantee of 24/7 regional support or sector‑specific certifications. Confirm multi‑region delivery SLAs and verify customer references in similar regulatory environments.

Buyers that treat Inner Circle status as one input among many—backed by reference checks, architecture reviews and measurable KPIs—are most likely to convert the credential into lasting, well‑governed outcomes.

---

Practical procurement checklist for enterprises evaluating Sunrise (or any Inner Circle partner)​

• Request measurable case studies that include KPIs (time saved, adoption, cost reductions) for Copilot + Dynamics 365 projects.
• Require governance artifacts: model cards, red‑team summaries, lineage documentation, drift detection processes, and incident playbooks.
• Verify architecture portability: ask for diagrams that separate data, models, connectors, and UI layers; insist on documented exit paths.
• Model three‑year TCO including Azure consumption forecasts, Copilot inference estimates, licensing scenarios, and managed service fees.
• Negotiate AI‑specific SLAs: accuracy/response metrics, drift detection windows, rollback procedures, and scheduled retraining windows.
• Validate operational scale: confirm 24/7 support, multi‑region capability, and detailed client references in regulated industries.

This checklist reflects best practice guidance that many procurement teams are adopting as Copilot and agentic workflows move from experiment to mission‑critical operations. Public analysis of Inner Circle announcements for 2025 underscores these same buyer priorities.

---

Market context — how Microsoft is using Inner Circle partners in 2025​

Microsoft’s partner program and the Inner Circle cohort are core levers in the broader push to scale enterprise AI across Dynamics 365, Power Platform and Microsoft Copilot scenarios. The 2025‑2026 round of Inner Circle announcements includes a range of global players—indicating Microsoft is concentrating co‑engineering and co‑sell resources among a small set of partners to accelerate production deployments. Other recognized partners in 2025 (across press releases) emphasize the same platform priorities and practical benefits: early roadmap visibility, prioritized engineering support and stronger co‑sell alignment. This pattern shows Microsoft’s strategic shift to partner‑led scale for AI Business Solutions.

---

Technical considerations for implementation teams​

Data and model governance​

• Ensure data lineage is traceable from ingestion to model output and that audit logs capture prompts, responses and downstream actions.
• Demand model validation evidence: test coverage across corner cases, red‑team results for safety, and procedures for prompt/behavioral adjustments.
• Confirm data residency and encryption policies align with regulatory requirements for the business’ jurisdictions.

Observability and agent management​

• Require observability tooling that records agent decision traces, execution timelines, and human intervention points.
• Verify agent orchestration approaches include throttling, quota controls, and cost monitoring to manage Azure inference consumption.
• Insist on role‑based access controls for agent configuration and prompt management to reduce insider risk.

CI/CD, testing and low‑code governance​

• For Power Platform components, include version control, automated testing, and deployment pipelines to manage rapid change.
• Ensure governance over low‑code artifacts so Power Apps and Power Automate flows are discoverable, auditable, and rolled out under controlled release processes.

These technical disciplines convert promising Copilot/Dynamics prototypes into sustainable production systems; they are the areas where a seasoned Inner Circle partner can demonstrate real differentiation, provided they supply transparent operational artifacts.

---

What Sunrise needs to do to convert recognition into lasting advantage​

Recognition alone is not a moat. To translate Inner Circle membership into durable competitive advantage, Sunrise should:

• Productize IP — turn bespoke implementations into packaged, licenseable accelerators with measurable SLAs and clear upgrade paths.
• Publish governance playbooks — public whitepapers and audit artifacts that help buyers understand the partner’s approach to responsible AI.
• Strengthen co‑sell plays — jointly staffed proofs‑of‑value with Microsoft and marquee references that illustrate scaled production deployments.
• Demonstrate portability options — documented separation of concerns that enables customers to protect against unplanned vendor lock‑in.
• Offer predictable pricing constructs — managed‑service tiers and consumption bands to reduce TCO variability for heavy Copilot/agent workloads.

These are pragmatic moves that buyers and analysts expect from Inner Circle partners that wish to move beyond marketing recognition to long‑term market share and margin strength. Industry coverage of other Inner Circle firms in 2025 highlights similar playbooks as the most successful path forward.

---

Conclusion​

Sunrise Technologies’ selection for the 2025–2026 Microsoft AI Business Solutions Inner Circle is a verifiable recognition of the company’s commercial performance and strategic alignment with Microsoft’s AI Business Applications agenda. The award provides concrete operational benefits—early roadmap access, prioritized engineering channels, and executive‑level briefings—that can accelerate the deployment of Copilot‑augmented Dynamics 365 and Power Platform solutions in retail and supply‑chain contexts.
At the same time, the recognition is not a substitute for rigorous procurement practice. Microsoft’s Inner Circle selection metrics are proprietary, and the badge should be treated as a strong signal rather than an audited guarantee. Buyers should demand demonstrable governance, portable architectures, predictable TCO, and production references before committing to large, Copilot‑driven transformation programs. The practical value of Inner Circle membership will be determined by whether partners like Sunrise can back their claims with measurable outcomes, operational playbooks, and transparent SLAs that address the new governance and cost realities introduced by enterprise AI.

---

Sunrise’s 2025 announcement continues a documented pattern of Microsoft collaboration and recognition across Business Applications cycles; for organizations seeking to accelerate retail and supply chain modernization on Dynamics 365 with Copilot and Power Platform, Sunrise’s Inner Circle placement is a meaningful data point—one that should be verified and expanded into contractual commitments and technical audits before large‑scale adoption.

---

Source: StreetInsider Sunrise Technologies achieves the 2025-2026 Microsoft AI Business Solutions Inner Circle award