{"id":237367,"date":"2026-01-21T09:54:30","date_gmt":"2026-01-21T09:54:30","guid":{"rendered":"https:\/\/osmosys.co\/uk\/?p=237367"},"modified":"2026-01-21T09:54:35","modified_gmt":"2026-01-21T09:54:35","slug":"ai-first-copilot-adoption-real-world","status":"publish","type":"post","link":"https:\/\/osmosys.co\/uk\/ai-first-copilot-adoption-real-world\/","title":{"rendered":"Copilot in the Real World: Adopting AI-First Strategies That Deliver Results"},"content":{"rendered":"<div id=\"bsf_rt_marker\"><\/div>\n<p>A large UK government experiment reported that Microsoft 365 Copilot users saved time on everyday tasks and reported improvements in work quality\u2014at a scale that looks a lot like the complexity many enterprises deal with.<br>A separate Microsoft customer story described public-sector employees saving <strong>around 10 hours per month<\/strong> with Microsoft 365 Copilot.<\/p>\n\n\n\n<p>Those examples are useful for one reason: they set the bar correctly.<\/p>\n\n\n\n<p>An <strong><a href=\"https:\/\/osmosys.co\/blog\/ai-checklist-dynamics-365-power-platform\/\">AI-first strategy<\/a><\/strong> is not \u201cwe bought licenses.\u201d It\u2019s:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>picking the right workflows,<\/li>\n\n\n\n<li>preparing the data those workflows depend on,<\/li>\n\n\n\n<li>training people to use Copilot responsibly,<\/li>\n\n\n\n<li>putting governance around what can go wrong,<\/li>\n\n\n\n<li>and tracking whether any of this is improving outcomes.<\/li>\n<\/ul>\n\n\n\n<p>This post is a practical playbook for adopting Copilot across business workflows\u2014grounded in what\u2019s working in real organizations, with region-specific considerations for ANZ, the US, and Canada.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What \u201cAI-first\u201d means in a Microsoft enterprise<\/h2>\n\n\n\n<p>In a Microsoft stack, \u201cAI-first\u201d usually means you\u2019re enabling <strong>Copilot experiences where work already happens<\/strong>:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>in productivity tools (Microsoft 365),<\/li>\n\n\n\n<li>in software delivery (GitHub),<\/li>\n\n\n\n<li>in business systems (Dynamics 365),<\/li>\n\n\n\n<li>in low-code automation and apps (Power Platform),<\/li>\n\n\n\n<li>and, increasingly, in custom agents (Copilot Studio).<\/li>\n<\/ul>\n\n\n\n<p>The win is rarely \u201cone perfect assistant.\u201d It\u2019s <strong>small improvements across high-frequency workflows<\/strong>\u2014summaries, follow-ups, drafts, retrieval, classification, next-best actions\u2014paired with the guardrails that keep risk acceptable.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">The Copilot family (and where each one fits)<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Microsoft 365 Copilot: grounded in your work context<\/h3>\n\n\n\n<p>Microsoft 365 Copilot is designed to help users with work tasks inside Microsoft 365 apps and experiences, grounded in organizational content users already have access to.<\/p>\n\n\n\n<p><strong>Where it shows up:<\/strong> Teams meeting summaries, Outlook thread catch-up, Word drafting, PowerPoint creation, Excel analysis.<\/p>\n\n\n\n<p><strong>Best fit workflows:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>meeting-to-actions<\/li>\n\n\n\n<li>drafting and rewriting<\/li>\n\n\n\n<li>search and synthesis across internal content<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">GitHub Copilot: for engineering velocity (with guardrails)<\/h3>\n\n\n\n<p>GitHub Copilot supports developers while they write and review code, with documentation that covers setup and organizational management.<\/p>\n\n\n\n<p><strong>Best fit workflows:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>boilerplate generation<\/li>\n\n\n\n<li>test scaffolding<\/li>\n\n\n\n<li>code explanations<\/li>\n\n\n\n<li>PR assistance (with human review)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Dynamics 365 Copilot: AI in customer-facing operations<\/h3>\n\n\n\n<p>Microsoft provides Copilot capabilities inside Dynamics 365 apps, with product-specific documentation across sales, service, and more.<\/p>\n\n\n\n<p><strong>Best fit workflows:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>opportunity\/account summaries<\/li>\n\n\n\n<li>meeting prep<\/li>\n\n\n\n<li>follow-up drafts<\/li>\n\n\n\n<li>case summaries and suggested responses<\/li>\n\n\n\n<li>call notes and action capture<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Power Platform Copilot: for makers and process owners<\/h3>\n\n\n\n<p>Copilot capabilities in Power Platform (Power Apps, Power Automate, Power Pages, Copilot Studio) are documented as part of the platform\u2019s generative capabilities.<\/p>\n\n\n\n<p><strong>Best fit workflows:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>\u201cdescribe what you need\u201d app creation starters<\/li>\n\n\n\n<li>flow creation and refinement<\/li>\n\n\n\n<li>turning business intent into a first draft solution<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Copilot Studio: when you need custom agents<\/h3>\n\n\n\n<p>Copilot Studio is positioned for building and deploying agents across channels with organizational controls.<\/p>\n\n\n\n<p><strong>Best fit workflows:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>guided internal help (policy, IT, HR)<\/li>\n\n\n\n<li>knowledge-grounded Q&amp;A over approved sources<\/li>\n\n\n\n<li>controlled action-taking where humans remain accountable<\/li>\n<\/ul>\n\n\n\n<figure class=\"wp-block-image size-full\"><img decoding=\"async\" data-src=\"https:\/\/osmosys.co\/wp-content\/uploads\/2026\/01\/2-1.png\" alt=\"Microsoft Connected Customer Journey with AI\" class=\"wp-image-239657 lazyload\" src=\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\" \/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Case example: ANZ\u2019s adoption pattern (and what\u2019s transferable)<\/h2>\n\n\n\n<p>ANZ\u2019s internal narrative is useful because it focuses on <strong>capability-building<\/strong>, not just tooling. An ANZ BlueNotes article describes supporting the employee experience for <strong>45,000 employees<\/strong> and building AI literacy while expanding access to tools like Microsoft 365 Copilot and GitHub Copilot.<br>ANZ also announced an AI Immersion Centre and reported purchasing Copilot for Microsoft 365 licenses to support hands-on learning and safe adoption.<\/p>\n\n\n\n<p>What\u2019s transferable (regardless of industry):<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Adoption is a skill, not an install.<\/strong><br>People need usage patterns (prompts, review habits, safe sharing norms) before \u201cAI-first\u201d becomes real.<\/li>\n\n\n\n<li><strong>Leadership enablement matters.<\/strong><br>Training leaders and champions accelerates practical use while keeping risk conversations honest.<\/li>\n\n\n\n<li><strong>Responsible use is part of the story.<\/strong><br>The ANZ approach repeatedly ties adoption to safe use and regulatory expectations, which is exactly the posture enterprise buyers want.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">A practical rollout framework that holds up in the real world<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Phase 1: Choose workflows (not departments)<\/h3>\n\n\n\n<p>Start with 3\u20135 workflows that are:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>high-frequency,<\/li>\n\n\n\n<li>text-heavy,<\/li>\n\n\n\n<li>and already stuck in meetings, inbox, or CRM notes.<\/li>\n<\/ul>\n\n\n\n<p>Examples:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>sales: meeting prep \u2192 follow-up \u2192 CRM updates<\/li>\n\n\n\n<li>service: case summary \u2192 suggested response \u2192 knowledge lookup<\/li>\n\n\n\n<li>operations: policy drafting \u2192 review cycle \u2192 stakeholder recap<\/li>\n\n\n\n<li>engineering: unit test scaffolding \u2192 code explanation \u2192 PR review prep<\/li>\n<\/ul>\n\n\n\n<p><strong>Implementation caveat:<\/strong> avoid \u201cblanket rollout\u201d as your first move. Copilot value varies by role and work pattern.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Phase 2: Data readiness and access boundaries<\/h3>\n\n\n\n<p>Copilot will only be as useful as the content it can safely reference. Microsoft documentation emphasizes grounding responses in content users are permitted to access.<\/p>\n\n\n\n<p>Practical readiness checks:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Are Teams\/SharePoint naming conventions usable?<\/li>\n\n\n\n<li>Are sensitive documents properly labeled and permissioned?<\/li>\n\n\n\n<li>Is CRM data complete enough to summarize without hallucinated gaps?<\/li>\n\n\n\n<li>Are knowledge bases current and searchable?<\/li>\n<\/ul>\n\n\n\n<p><strong>Implementation caveat:<\/strong> permission sprawl becomes \u201canswer sprawl.\u201d Fix the access model first.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Phase 3: Governance + human accountability (make it simple and explicit)<\/h3>\n\n\n\n<p>This is not about writing a 40-page policy. It\u2019s about agreeing on:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>what users can do with Copilot,<\/li>\n\n\n\n<li>what must be reviewed,<\/li>\n\n\n\n<li>what must never be generated automatically,<\/li>\n\n\n\n<li>and how you\u2019ll handle mistakes.<\/li>\n<\/ul>\n\n\n\n<p><strong>High-impact guardrails:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>clear \u201chuman owns the outcome\u201d statement<\/li>\n\n\n\n<li>sensitivity rules (what content can be used in prompts)<\/li>\n\n\n\n<li>approved use cases vs restricted use cases<\/li>\n\n\n\n<li>escalation path for unsafe output or data exposure concerns<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Phase 4: Adoption + measurement loops<\/h3>\n\n\n\n<p>If you don\u2019t measure outcomes, adoption becomes vibes.<\/p>\n\n\n\n<p>Use a simple measurement model:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>baseline<\/strong> (before)<\/li>\n\n\n\n<li><strong>pilot<\/strong> (with training)<\/li>\n\n\n\n<li><strong>stabilize<\/strong> (with guardrails)<\/li>\n\n\n\n<li><strong>scale<\/strong> (only where metrics support it)<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Implementation checklist (copy\/paste into your rollout plan)<\/h2>\n\n\n\n<p>Use this as your minimum \u201cdone means done\u201d list:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Pick 3\u20135 workflows with clear owners and success criteria.<\/li>\n\n\n\n<li>Confirm data sources and permission boundaries for each workflow.<\/li>\n\n\n\n<li>Publish a one-page usage policy (what\u2019s allowed, what\u2019s not).<\/li>\n\n\n\n<li>Create a prompt starter pack per role (sales, service, ops, dev).<\/li>\n\n\n\n<li>Train pilot users on review habits (verify, cite, re-check).<\/li>\n\n\n\n<li>Define human approval points for customer-facing outputs.<\/li>\n\n\n\n<li>Establish reporting for adoption signals (usage, satisfaction, blockers).<\/li>\n\n\n\n<li>Track outcome metrics tied to the workflow (see next section).<\/li>\n\n\n\n<li>Run a weekly \u201cwhat worked \/ what broke\u201d feedback loop.<\/li>\n\n\n\n<li>Expand only after workflows show repeatable value and acceptable risk.<\/li>\n\n\n\n<li>Document known failure modes and mitigation playbooks.<\/li>\n\n\n\n<li>Revisit governance quarterly as features evolve and usage grows.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">What to measure (without pretending one KPI fits everyone)<\/h2>\n\n\n\n<p>Pick 2\u20133 outcome metrics per workflow:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Productivity and cycle-time metrics<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>time spent searching for information (self-reported + tooling signals)<\/li>\n\n\n\n<li>time from meeting \u2192 follow-up sent<\/li>\n\n\n\n<li>time from case open \u2192 first quality response drafted<\/li>\n\n\n\n<li>time from lead created \u2192 first outreach<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Quality and consistency metrics<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>fewer missed follow-ups (sales\/service)<\/li>\n\n\n\n<li>better structured notes and summaries<\/li>\n\n\n\n<li>improved knowledge article reuse<\/li>\n\n\n\n<li>reduced rework due to unclear handoffs<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Risk and control metrics<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>number of policy violations (or near-misses) reported<\/li>\n\n\n\n<li>percentage of customer-facing content reviewed before send<\/li>\n\n\n\n<li>sensitivity label compliance on shared artifacts<\/li>\n<\/ul>\n\n\n\n<p>If you want a credible benchmark for \u201ctime saved\u201d language, cite pilot-style studies rather than guessing. For example, the UK cross-government experiment reports an average daily time saving and related user feedback signals.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Pitfalls to avoid (the ones that quietly kill adoption)<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">1) Rolling out tools before fixing information hygiene<\/h3>\n\n\n\n<p>If your CRM fields are inconsistent and your knowledge base is stale, Copilot will surface that reality faster. Users will blame the tool, but the root cause is data quality.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">2) Treating Copilot as an autopilot<\/h3>\n\n\n\n<p>Copilot can draft. It cannot own accountability.<br>Set expectations early: the user reviews, edits, and owns what gets sent or committed.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">3) Skipping change management<\/h3>\n\n\n\n<p>Most failures look like this:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>people don\u2019t know what good prompts look like,<\/li>\n\n\n\n<li>they don\u2019t trust outputs,<\/li>\n\n\n\n<li>and they quietly stop using it.<\/li>\n<\/ul>\n\n\n\n<p>Adoption needs small wins, role-based enablement, and feedback loops.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">4) Ignoring regional privacy expectations<\/h3>\n\n\n\n<p>You don\u2019t need legal detail in a blog, but you do need a clear posture:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Australia:<\/strong> privacy obligations are anchored in the Privacy Act and OAIC guidance; enterprises often want clarity on data handling and controls.<\/li>\n\n\n\n<li><strong>Canada:<\/strong> privacy expectations commonly reference PIPEDA at a federal level, with organizational responsibility for appropriate safeguards.<\/li>\n\n\n\n<li><strong>US:<\/strong> privacy is a patchwork (state laws + sector rules), and buyers tend to ask hard questions about security, access, and governance early.<\/li>\n<\/ul>\n\n\n\n<p><strong>Important:<\/strong> this is not legal advice. Use these as cues for what stakeholders will ask, and validate requirements with your legal\/compliance teams.<\/p>\n\n\n\n<p><strong>Diagram idea (simple and useful):<\/strong><br>A left-to-right workflow showing:<\/p>\n\n\n\n<p><strong>Teams meeting \u2192 Copilot summary \u2192 tasks created in Planner\/To Do \u2192 Dynamics 365 opportunity update \u2192 Power Automate notification to next owner \u2192 dashboard view<\/strong><\/p>\n\n\n\n<p>Caption: \u201cCopilot adds value when it connects work artifacts to owned next steps.\u201d<\/p>\n\n\n\n<p>(Optional) Embed a short Microsoft Copilot overview video in this section if your WordPress setup supports it.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Bringing it back to Dynamics 365: where Copilot creates compounding value<\/h2>\n\n\n\n<p>Most organizations don\u2019t struggle to \u201cuse AI.\u201d They struggle to <strong>connect actions back to systems of record<\/strong>.<\/p>\n\n\n\n<p>Dynamics 365 Copilot capabilities (sales\/service) are most valuable when they reduce the friction between:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>conversations,<\/li>\n\n\n\n<li>notes,<\/li>\n\n\n\n<li>follow-ups,<\/li>\n\n\n\n<li>and CRM updates.<\/li>\n<\/ul>\n\n\n\n<p>That\u2019s where AI-first becomes visible to leadership: cleaner pipeline hygiene, faster follow-up, clearer case work, and fewer dropped handoffs.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Book an AI Opportunity Workshop with Osmosys<\/h2>\n\n\n\n<p>If you\u2019re evaluating Copilot (or already piloting it) and want a clear, outcome-driven adoption plan, Osmosys can help you run an <strong>AI Opportunity Workshop<\/strong>:<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><a href=\"https:\/\/osmosys.co\/book-a-demo-2\/\"><img decoding=\"async\" data-src=\"https:\/\/osmosys.co\/wp-content\/uploads\/2026\/01\/3-1.png\" alt=\"Copilot in Dynamics 365 Sales overview with AI\" class=\"wp-image-239658 lazyload\" src=\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\" \/><\/a><\/figure>\n\n\n\n<p>What you\u2019ll leave with:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>a prioritized shortlist of high-impact workflows,<\/li>\n\n\n\n<li>a readiness and governance checklist,<\/li>\n\n\n\n<li>a pilot plan with success metrics,<\/li>\n\n\n\n<li>and a practical rollout sequence across Dynamics 365, Power Platform, and Microsoft 365.<\/li>\n<\/ul>\n\n\n\n<p><strong>Next step:<\/strong> <a href=\"https:\/\/osmosys.co\/book-a-demo-2\/\">Book an AI Opportunity Workshop with Osmosys.<\/a><\/p>\n\n\n<div id=\"rank-math-faq\" class=\"rank-math-block\">\n<div class=\"rank-math-list \">\n<div id=\"faq-question-1768979018652\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \">What\u2019s the difference between \u201cAI-first\u201d and \u201cAI everywhere\u201d?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>AI-first means you prioritize workflows where AI measurably improves outcomes, with governance and ownership. \u201cAI everywhere\u201d usually becomes scattered usage without clear results.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1768979032412\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \">Do we need perfect data before adopting Copilot?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>No. But you do need clear permission boundaries and a minimum data hygiene baseline for the workflows you\u2019re targeting, otherwise trust collapses quickly.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1768979044585\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \">How do we prevent over-reliance on Copilot outputs?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Make review habits part of training: verify facts, check sources, and keep humans accountable for final decisions and customer-facing communication.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1768979062846\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \">Which teams usually see value first?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Teams with high volumes of text-based work and repeated patterns\u2014sales, service, operations, and engineering\u2014often see faster wins, provided training and governance are in place.<\/p>\n\n<\/div>\n<\/div>\n<\/div>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>A large UK government experiment reported that Microsoft 365 Copilot users saved time on everyday tasks and reported improvements in work quality\u2014at a scale that looks a lot like the complexity many enterprises deal with.A separate Microsoft customer story described public-sector employees saving around 10 hours per month with Microsoft 365 Copilot. Those examples are [&hellip;]<\/p>\n","protected":false},"author":44,"featured_media":237368,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"off","_et_pb_old_content":"","_et_gb_content_width":"","_lmt_disableupdate":"","_lmt_disable":"","jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[75,143],"tags":[160,161,162,163,164,165,166],"class_list":["post-237367","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ai","category-ai-in-crm","tag-adoption","tag-ai-first-strategy","tag-change-management","tag-dynamics-365-copilot","tag-governance","tag-microsoft-copilot","tag-power-platform"],"modified_by":"mounika","jetpack_featured_media_url":"https:\/\/osmosys.co\/uk\/wp-content\/uploads\/sites\/6\/2026\/01\/1-1.png","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/osmosys.co\/uk\/wp-json\/wp\/v2\/posts\/237367","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/osmosys.co\/uk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/osmosys.co\/uk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/osmosys.co\/uk\/wp-json\/wp\/v2\/users\/44"}],"replies":[{"embeddable":true,"href":"https:\/\/osmosys.co\/uk\/wp-json\/wp\/v2\/comments?post=237367"}],"version-history":[{"count":1,"href":"https:\/\/osmosys.co\/uk\/wp-json\/wp\/v2\/posts\/237367\/revisions"}],"predecessor-version":[{"id":237369,"href":"https:\/\/osmosys.co\/uk\/wp-json\/wp\/v2\/posts\/237367\/revisions\/237369"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/osmosys.co\/uk\/wp-json\/wp\/v2\/media\/237368"}],"wp:attachment":[{"href":"https:\/\/osmosys.co\/uk\/wp-json\/wp\/v2\/media?parent=237367"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/osmosys.co\/uk\/wp-json\/wp\/v2\/categories?post=237367"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/osmosys.co\/uk\/wp-json\/wp\/v2\/tags?post=237367"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}