Land Your Offer - Anatomy of Revenue Generating Partner Offer - Part 4 - Cowork
So far this series has followed Copilot from a first trial (Part 1), through funded envisioning (Part 2), to a full rollout (Part 3). Part 4 turns to the newest step on that path: getting people to hand real, multi-step work to Copilot Cowork. This motion is different from the first three. There are no engagement hours to log and no T-shirt sizes to choose. Everything rides on one number: how many more people are using Cowork after three months. Grow that number and the rest follows. Microsoft has also announced that usage-based billing will be on by default for new Microsoft 365 Copilot Business licences bought through CSP from 1 December 2026, which removes a setup step between a customer and their first Cowork task. When what counts is the outcome rather than the effort, the winning approach is a fixed sequence you can run the same way for every customer. Where Cowork Fits Among the Copilot Experiences Every activation begins with the same conversation. Customers now have four ways to work with Copilot, and the first step is knowing which one suits which job. Chat Cowork Code Autopilot What it does Secure, fast AI for everyday questions, drafts and ideas Plans and carries out multi-step work across apps, files and systems Turns ideas into dashboards, trackers and apps An always-on personal agent with a name, a role and a goal Best for Quick, focused tasks in one conversation Complex jobs that pull several sources together into a finished result Reusable working solutions people return to Work that unfolds over days, such as chasing decisions and commitments How long it runs Seconds to minutes Minutes to hours, on its own Depends on what is being built Continuously, in the background Typical uses Daily briefing, project summary, content drafts Board preparation, financial close, contract review, campaign launch Team dashboards, recurring-task tools Flagging stalled decisions, resolving calendar clashes Cowork is the right home for work that takes multiple steps, spans two or more apps, and ends in an action such as an update, an approval or a routed request. Purely informational tasks stay in Chat. Built to Repeat: Why This Motion Scales Helping customers move that kind of work into Cowork looks much the same from one tenant to the next, and that is what makes this motion worth building. Design it once, and every new tenant reuses the same steps: The same lead-in. Readiness, licensing and billing checks take about four weeks and follow one checklist. The same assessment. Every pilot user runs one prompt that reads their recent work and tells you whether Cowork fits. The same sixty scenarios. Ten proven scenarios in each of six business functions, landed in the same order over three weeks. The same milestones. 50 active users and $2,500 of monthly Cowork usage in Month 1, held through Month 3. Reuse that compounds. Scenarios that work become shared Cowork skills, so each new tenant starts further ahead than the last. That consistency is what makes the motion predictable. The twelve-week activation does not need to carry a customer fee: Microsoft's partner programs reward the growth it creates, and what you realise rises as the customer brings more users on board. The monthly service that follows adds a further layer on top of that, one that keeps building long after the activation window closes. Package and sell it through whichever route your customers already use, whether directly, through your distributor, as a private offer, or as a listing in Microsoft Marketplace. The packaging is the easy part once the activities are the same every time. Sixty Scenarios Across Six Functions The most reusable of those activities is the scenario library: ten scenarios per function across all six, landed during Month 1. Each one is real delegated work, not a single prompt. Function Ten scenarios to land Executives Executive command centre; inbox triage at scale; board pre-reads; cross-org leadership briefs; weekly meeting synthesis; decision briefings; delegated memo and deck; performance analytics; relationship briefings; out-of-office handoffs Sales Meeting prep and follow-up; RFP responses; branded pitch and proposal; account research briefs; pipeline gap analysis; pipeline risk reviews; renewal and QBR prep; expansion identification; customer onboarding; ROI value stories Marketing Branded asset sets; launch activation kits; messaging and positioning docs; performance readouts; content drift audits; campaign kickoff; event command centre; customer-signal synthesis; competitive response; post-launch optimisation Customer Service Case-intake briefs; root-cause diagnosis; knowledge-cited replies; SLA-risk triage; stalled-case outreach; manager interventions; escalation handoffs; voice-of-customer synthesis; service operations review; coaching and training Finance and Operations Close and variance packages; weekly business review; reconciliation reviews; audit evidence packages; RFQ response builder; procurement bid-to-award; regulatory response; master-data automation; expense itemisation; market intelligence reports Legal Playbook contract review; draft from precedent; portfolio key terms extraction; playbook from precedents; map how contracts fit together; tracked-change editing; obligations and deadlines tracker; final draft check; case chronology; regulatory gaps Add Each User's Own Workflows with the Cowork Investment Advisor The sixty scenarios are a proven starting list. The Cowork Investment Advisor, the agent behind the Cowork Investment Assessment used throughout this playbook, finds the work that is specific to each person. It reads their Work IQ signals (emails, meetings, documents, chats and collaboration patterns) and returns: Persona: the role their work patterns point to, so you know which of the six functions to draw scenarios from. Top three workflows: the user's own tasks that qualify for Cowork, each rated Light, Medium or Heavy. Cost and return: estimated credits, pay-as-you-go and pre-purchase cost, and the return on that spend. Verdict: Yes (two or more qualifying workflows across two or more teams), Yes with a pilot (one workflow) or Not yet (none). A workflow only qualifies when it runs multiple steps, moves data between two or more apps, ends in a business action, includes decision points and tracks its own progress. Purely informational work is pointed to Copilot Chat, Copilot Pages or scheduled prompts instead. Choose the format that fits who is running it: a prompt any Copilot user can paste into Copilot Chat, an Agent Builder version a team lead can share, or a pre-built agent IT can deploy across the organisation. Run it alongside the scenario rollout, not ahead of it, and feed its results into the Customer Cowork Estimator to size credit spend. The Rules of the Window, Made Simple Scenarios and the assessment build the usage. A short set of rules decides when that usage counts. Which customers fit: at the August 2026 baseline, the customer has Microsoft 365 Copilot with Cowork enabled, fewer than 50 Cowork monthly active users and less than $2,500 of monthly Cowork consumption. At least half of their Copilot licences and Cowork consumption must come through CSP. Strategic 500 customers are excluded. What starts the clock: the first month the customer reaches at least 50 Cowork monthly active users and at least $2,500 of monthly Cowork consumption becomes Month 1 of a three-month window. What decides the payment: both thresholds must still be met in Month 3. Month 2 does not count towards qualifying, but it builds the usage Month 3 is measured on. How much: $50 for each qualified new user. Qualified new users are the lower of two numbers: Month 3 users minus August users, or extra monthly consumption divided by $50. The payment is at least $200 and at most $12,500 per tenant, which is 250 new users. When: 45 days after the window closes, paid as a rebate. It comes on top of your CSP consumption earnings. How often: once per customer tenant for the life of the incentive. If Month 3 falls short, the window lapses and a new one can start the next month both thresholds are met. June 2027 is the last month a window can start. Who can claim: partners with a Solutions Partner designation in Modern Work, Business Applications, Infrastructure, Data & AI or Digital & App Innovation, plus $1M (direct bill) or $25K (indirect reseller) of trailing 12-month revenue. Indirect resellers can qualify with 25 capability points instead of a designation. No Copilot specialization is needed. Attribution: the same partner must be transacting partner of record for both the Copilot licences and the Azure subscription that carries the Cowork consumption. Term: 1 September 2026 to 30 June 2027. What You Do in Each Stage Those rules shape a motion with four stages: Qualify, Activate, Sustain and Reward. Qualify (four weeks before Month 1): confirm you meet the partner requirements and finish your Partner Center setup. Find customers who meet the August baseline. Set yourself as transacting partner of record for licences and consumption. Move Cowork billing onto a CSP Azure plan with Owner or Contributor access, so Partner Earned Credit applies, and switch on the default spending policy. Activate (Month 1): two independent tracks run side by side; the assessment can start in the lead-in, and neither waits for the other. Assess the work: ask each pilot user to run the Cowork Investment Assessment, either as an agent or by pasting its prompt into Copilot Chat. It reviews three to six months of their work and answers Yes, Yes with a pilot, or Not yet, showing where Cowork adds the most value. Land the scenarios: roll out the six functions on a weekly rhythm: Executives and Sales in week 1, Marketing and Customer Service in week 2, then Finance and Operations and Legal in week 3. Keep usage unblocked: budget about $50 per user a month (roughly 5,000 credits) and set a Cowork spending limit of 250,000 credits or more a month, with alerts, so usage can reach the week 4 milestone without hitting a cap. Sustain (Months 2 and 3): save the scenarios that work as shared Cowork skills any team can reuse, and add pilot users to keep active users above 50. Check users, credits and attribution every week in Cost management in the Microsoft 365 admin center. Approve credit requests quickly and recover any dip before Month 3. Reward (after Month 3): calculate qualified new users, expect payment about six weeks after the window closes, and move the customer onto the monthly managed services. The tenant can only be paid once, so the next activation payment comes from the next tenant. Every Step, Week by Week Each stage breaks down into the steps below, and the same plan works for any eligible tenant. Timing is recommended pacing, not a program rule. Wk 1 is the first week of Month 1, and negative weeks are the lead-in before it. ID Stage Activity Timing (week) Exit Criteria Pre-req Customer fit Customer meets the August 2026 baseline Aug 2026 Copilot with Cowork enabled; under 50 Cowork users and under $2,500 monthly consumption; at least half bought through CSP; not Strategic 500 Q1 Qualify Confirm partner eligibility Wk -4 Solutions Partner designation and $1M (direct bill) or $25K (indirect reseller) trailing 12-month revenue Q2 Qualify Enrol and finish Partner Center setup Wk -4 to -3 Partner program agreement, incentive enrolment and CSP authorization in place; identity, tax and banking details accepted Q3 Qualify Find eligible customers Wk -3 Customer meets the August 2026 baseline Q4 Qualify Set attribution Wk -2 One partner is transacting partner of record for the Copilot licences and the Azure subscription carrying Cowork consumption Q5 Qualify Set up Partner Earned Credit and cost management billing Wk -2 to -1 CSP Azure plan with Owner or Contributor access (or Azure Lighthouse); default spending policy on, billed pay as you go A1 Activate Run the Cowork Investment Assessment Wk -2 to -1 Each pilot user rated Yes (2+ workflows across 2+ teams), Yes with a pilot (1 workflow) or Not yet A2 Activate Land Executives scenarios Wk 1 For example: command centre, board pre-reads A3 Activate Land Sales scenarios Wk 1 For example: pipeline risk reviews, RFP responses A4 Activate Land Marketing scenarios Wk 2 For example: launch activation kits, campaign kickoff A5 Activate Land Customer Service scenarios Wk 2 For example: SLA-risk triage, stalled-case outreach A6 Activate Land Finance and Operations scenarios Wk 3 For example: close and variance packages, audit evidence A7 Activate Land Legal scenarios Wk 3 For example: playbook contract review, obligations tracker A8 Activate Reach both thresholds Wk 4 50+ Cowork users and $2,500+ monthly consumption; attribution confirmed; spending limit of at least 250,000 credits a month S1 Sustain Turn proven scenarios into shared Cowork skills Wk 5 to 8 (Month 2) Skills reusable across teams; pilot users added to stay above 50 S2 Sustain Watch usage every week Wk 1 to 12 Users, credits and attribution checked weekly; limits tuned; dips fixed before Month 3 S3 Sustain Hold or grow usage Wk 9 to 12 (Month 3) Both thresholds still met and attribution unchanged; Month 3 results set the payment S4 Sustain Start a new window if needed Wk 13+ A new window opens the next month both thresholds are met; June 2027 is the last start R1 Reward Work out qualified new users End of Wk 12 Lower of (Month 3 users minus August users) and (extra monthly consumption ÷ $50), rounded down R2 Reward Apply the rate and limits End of Wk 12 $50 per qualified user as a full rebate; $200 minimum, $12,500 maximum per tenant R3 Reward Receive payment ~Wk 18 Paid 45 days after the window closes R4 Reward Keep growing through managed services Wk 19+ The activation payment does not repeat for this tenant; from here, managed services carry the growth: Cowork adoption and support and AI FinOps and governance every month, plus Cowork scale-out to new teams, and to new tenants that can start their own window Layer by Layer: What One Tenant Returns Run those steps on one tenant and three returns stack up during the window. Here is how they add up for a customer that starts from zero Cowork usage. Earning How it is worked out 50 new users At the cap: 250 new users Cowork CSP Activation Incentive $50 for each qualified new user, paid 45 days after Month 3 $2.5K $12.5K CSP incentive on Copilot Credits† 13% of monthly Cowork consumption (3% core plus 10% growth), over the three months ~$0.98K ~$4.88K Partner Earned Credit† 13% of monthly pay-as-you-go Cowork consumption on the customer's CSP Azure plan, while you hold eligible admin access, over the same three months ~$0.98K ~$4.88K Total per tenant, per window ~$4.5K ~$22.3K † Illustrative. Assumes $50 of monthly Cowork consumption per new user, so $2,500 a month at 50 users and $12,500 a month at 250. The CSP incentive is paid 60% as rebate and 40% as co-op. The 13% Partner Earned Credit rate is a planning figure; the rate that applies is the one in the Partner Center price list. Check every figure against the latest Microsoft Commercial Partner Incentives Guide. When Partner Earned Credit applies. All of the following must be true: You hold an active Microsoft AI Cloud Partner Program agreement and bill the customer's Azure plan through CSP. The Cowork consumption runs pay-as-you-go on that Azure plan. Reservations, savings plans, Spot virtual machines, and Marketplace or third-party products are excluded. You have admin access to the subscription through an eligible Azure role: the default admin on behalf of (AOBO) access, Azure Lighthouse, or user or service-principal accounts linked with Partner Admin Link. The role must sit at subscription, resource group or management group level, because root scope alone does not count. As an indirect reseller, your indirect provider grants you that role on the customer's subscription. The access stays in place. If the customer removes it, or the subscription moves to a new partner who does not set it up again, the credit stops. The credit is worked out daily and shows as a lower price on your invoice, not as a separate line. See Partner Earned Credit for managed services for the full rules. Those returns grow in two ways. First, the CSP incentive and Partner Earned Credit do not stop after Month 3. They continue every month the customer keeps using Cowork. Second, the activation payment is once per tenant, so the real scale comes from running the same twelve weeks across many tenants. To find them, filter the AI Business Solutions & Security Insights (ASPX) dashboard for customers you manage that have Copilot, Cowork usage below 50 users and a CSP relationship. Then line up a new cohort each month. The last window can start in June 2027, so every month you wait is one fewer cohort. How the Offer Fits Together: A Twelve-Week Run Plan The picture below puts one tenant's journey on a single page: the twelve weeks across the top and the returns underneath. Read it from left to right: Lead-in (four weeks before Month 1): eligibility, attribution, Partner Earned Credit and Default Spending policy are settled, and pilot users are rated by the assessment. Month 1 (weeks 1 to 4): two functions land each week, Executives with Sales, then Marketing with Customer Service, then Finance and Operations with Legal. Week 4 is the milestone: 50 users and $2,500 of consumption. Months 2 and 3 (weeks 5 to 12): champions, role-based training and new users run throughout. Proven scenarios become reusable skills in Month 2. Weekly monitoring keeps both numbers above the line until the final Month 3 check. Payout (about week 18): qualified users are calculated and the ~$2.5K activation payment arrives. The ~$0.98K CSP incentive and ~$0.98K Partner Earned Credit build up month by month along the way, bringing the window to about $4.5K per tenant before any managed services. Beyond the Payout: Services That Grow With Every New User The payout closes the activation, not the relationship. Keeping Cowork useful takes work every month, so group the services into three families: run adoption, support and FinOps as one subscription after Month 3, and add security and scale-out as the customer needs them. Service family What you run Cadence What the customer gets Cowork adoption and support Usage health monitoring: track active use by team and follow up on drop-offs 4 hours a month Drop-offs caught within the month. Each lapsed user means about $5.2K a year of time savings lost Cowork adoption and support Change management and enablement: champion network and role-based training 5 hours a month Each extra active user adds about $5.2K a year of time saved for about $600 of Cowork spend Cowork adoption and support Continual improvement: add new scenarios and build shared Cowork skills 1 day a month Time saved rises from 2 to 2.5 hours per user a week: about $65K more a year across 50 users Cowork adoption and support Service desk (first and second line): access issues, errors and how-to questions 8 hours a month Fixes by the next working day. Each stuck user loses about $100 a week of time savings AI FinOps and governance Copilot Credit optimisation: review credits by user, group and agent; tune the costliest tasks 1.5 hours a month 5 to 10% of waste removed: about $1.5K to $3K a year back on about $30K of Cowork spend AI FinOps and governance Spending policies: limits, alerts, credit requests, billing method and departmental chargeback 2 days to set up, then monthly tuning Monthly spend stays within 10% of the $2,500 plan, and invoices hold no surprises AI FinOps and governance Monthly business review with the sponsor: value against cost, next priorities 3 hours a month One scorecard: hours saved at $50 an hour against about $48K a year of Cowork and Copilot licences AI FinOps and governance Skill and automation lifecycle: test, update and retire shared skills and scheduled tasks 4 hours a month At $0.70 to $15 a run, each daily task nobody uses wastes about $250 to $5,500 a year until retired AI FinOps and governance Security and compliance monitoring: alerts on risky Cowork actions, oversharing and data loss events 24x7, as an add-on to an existing security operations service Risky actions triaged within an agreed time, for example one hour, at low extra cost Cowork scale-out Re-run the Investment Assessment for new teams or roles in the same tenant 1 week per group Spend goes only to Yes users: about $600 a year of Cowork each, returning about $5.2K of time saved Cowork scale-out Land and expand: discovery for new business units or tenants 2-week sprint Next three units sized. For example, 50 users save about $260K a year for about $48K of Cowork and Copilot Cowork scale-out Repeatable rollout: run the proven twelve weeks for each new unit or tenant About 3 months per rollout 50+ active users each time, reusing proven skills. New tenants can earn their own activation payment Total About 4.5 partner days a month / about 55 a year About $260K a year of time saved against about $103K of total cost: a return of about 2.5 times, rising towards 3 times at 100+ users The total row tells the story. Around $55K a year of service revenue from one tenant sits on top of the ~$4.5K earned in the activation window, and it repeats every year the customer keeps using Cowork. On the customer side, the $103K of total cost breaks down as $30K of Cowork, $18K of Copilot licences and $55K of services. As usage grows to 100 or more users in the year, Cowork spend rises to about $60K and the return climbs towards three times. Value figures are illustrative. They assume 2 hours saved per user a week at $50 an hour, Copilot at about $30 per user a month and a partner day rate of $1,000. Replace them with each customer's Investment Assessment results. Start Your First Tenant This Quarter Putting the playbook to work starts with one tenant. Six moves get you there: Check you qualify: confirm your Solutions Partner designation and revenue threshold, then enrol in the incentive and complete your Partner Center details. Find your tenants: in ASPX, filter for customers with Copilot, Cowork usage below 50 users and a CSP relationship. Confirm each one against the August 2026 baseline. Get the plumbing right first: attribution, the CSP Azure plan and the default spending policy all need to be in place before Month 1. A missed setup step cannot be fixed later in the window. Run the assessment in parallel: pilot users can take the Cowork Investment Assessment at any point. It never holds up the scenario rollout, and its results show where Cowork should grow next. Package it once: treat the twelve-week activation as an investment that pays back as users grow, then layer a monthly adoption, FinOps and scale-out service on top, sold through the routes your customers already buy from you. Put the Month 3 review in the diary on day one, together with the sponsor's first monthly business review. Cowork is where Copilot moves from answering questions to finishing work. Help every customer reach that point, one tenant at a time. Further Reading and Tools These resources cover the rules, the tools and the wider Copilot picture behind this playbook. Copilot Cowork CSP Activation Incentive Copilot Cowork Investment Assessment Copilot Credit Estimator Cowork Nifty-Sixty The new Copilot and the partner opportunity
Add custom attributes to users (or devices) to map hardware peripherals
Hello everyone, I am seeking some help, guidance or suggestions with the following situation. We are looking for a solution that could map peripherals (such as monitors) to a user or a device. Once we have that info, we will utilize an additional tool to extend our visibility over the assets & assignments. I reviewed a few documentations and videos about potential solutions, and I just want to know if that's possible or I should not invest time on it any longer. The scope is the following: 1. We've collected information about connected monitors using Intune Script detection. That's perfect. It already maps devices with monitor's serial numbers and other details. 2. Export in CSV is fine (although, the data is not a 100% accurate, we have an internal data base that we can compare). 3. Now, how can we properly map that data to the cloud objects? What the best approach is? Logically, the monitors should be added to the devices, but Intune Custom Attributes are not easily populated/managed (?). On the other hand, Entra AD is capable of managing such expressions and overall has better capabilities (or am I wrong?) when it comes to operating with cloud objects. I am really looking for a human response; more of a knowledge share. I'd appreciate if someone shares their experience with similar scenarios. :) I apologise in advance if my question is not in the right section. Docs: https://learn.microsoft.com/en-us/graph/extensibility-overview?tabs=http https://www.reddit.com/r/AZURE/comments/1e5z3kv/add_customextension_attribute_in_entra_id/ https://www.reddit.com/r/AZURE/comments/1dz4cru/comment/lcdf2ev/?context=3&share_id=UqZR0m9s-9SWiHOiVwwAM&utm_content=1&utm_medium=ios_app&utm_name=ioscss&utm_source=share&utm_term=1 https://www.youtube.com/watch?v=kBm-fjqg0PU https://www.youtube.com/watch?v=LHXfFoygiOA Thanks :)Microsoft Releases FY27 Q1 Results - 470 Million Microsoft 365 Users?
Every quarter, I look for interesting nuggets about Microsoft 365 and the wider Microsoft Cloud ecosystem in Microsoft’s quarterly results. This time round, the Microsoft Cloud clocked up $63.9 billion, which is a lot of money. Growth continues for Microsoft 365 in both revenues (spurred by Copilot, E7, and price increases) and numbers. The seat count is growing more slowly than in the past in percentage terms, but that’s because the base is so large. https://office365itpros.com/2026/10/30/microsoft-cloud-fy27-q1/
The support channels are failing miserably
I own a company and registered for a work account 2 years ago. We haven't purchased any Microsoft products yet, and I got logged out of authenticator. We're in a vicious cycle where logging in requires authenticator and authenticator requires authenticator. I called technical support Monday and was told to sign up for new account to log a ticket. Mid-way through the call the agent said his shift ended in 2 minutes and he would call me back Tuesday. He never called back. I followed up and waited on hold for the data and privacy department for 45 minutes 3 times, and each time the call dropped. I tried using the support agent and it won't help me, because it says I'm not the global admin on any of my accounts (this makes no sense). Are there any channels for escalating this? We would like to buy Microsoft 365 for our business, but now I am terrified of doing this, because it seems like there is no way to get technical support.Copilot, Microsoft 365 & Power Platform Community call
💡 Copilot, Microsoft 365 & Power Platform weekly community call focuses on different use cases and features within the Microsoft 365 and Power Platform - across Microsoft 365 Copilot, Copilot Studio, SharePoint, Power Apps and more. Demos in this call are presented by the community members. 👏 Looking to catch up on the latest news and updates, including cool community demos, this call is for you! 📅 On 5th of November we'll have following agenda: Latest news and events from Microsoft Latest on Copilot prompt of the week CommunityDays.org update Microsoft 365 Maturity model PnP Framework and Core SDK extension PnP PowerShell Script samples Copilot pro dev samples Power Platform samples Demos this time Vijay Kumar Gilakattula – Content Rollup aggregate news across SharePoint sites with Microsoft Search Marc André Schröder-Zhou – Creating UX component solution to manage approvals directly in Copilot canvas Adam Wójcik - Announcing new and updated PnP Provisioning engine for M365 provisioning automation 📅 Download recurrent invite from https://aka.ms/community/m365-powerplat-dev-call-invite 📞 & 📺 Join the Microsoft Teams meeting live at https://aka.ms/community/m365-powerplat-dev-call-join 💡 Building something cool for Microsoft 365 or Power Platform (Copilot, SharePoint, Power Apps, etc)? We are always looking for presenters - Volunteer for a community call demo at https://aka.ms/community/request/demo 👋 See you in the call! 📖 Resources: Previous community call recordings and demos from the Microsoft Community Learning YouTube channel at https://aka.ms/community/youtube Microsoft 365 & Power Platform samples from Microsoft and community - https://aka.ms/community/samples Microsoft 365 & Power Platform community details - https://aka.ms/community/home 🧡 Sharing is caring!Copilot, Microsoft 365 & Power Platform product updates call
💡Copilot, Microsoft 365 & Power Platform product updates call concentrates on the different use cases and features within the Microsoft 365 and in Power Platform. Call includes topics like Microsoft 365 Copilot, Copilot Studio, Microsoft Teams, Power Platform, Microsoft Graph, Microsoft Viva, Microsoft Search, Microsoft Lists, SharePoint, Power Automate, Power Apps and more. 👏 Weekly Tuesday call is for all community members to see Microsoft PMs, engineering and Cloud Advocates showcasing the art of possible with Copilot, Microsoft 365 and Power Platform. 📅 On the 3rd of November we'll have following agenda: News and updates from Microsoft Together mode group photo Joe Komban - Copilot in SharePoint: New Skills Management Experience and Productivity Features Paolo Pialorsi - Building Copilot Cowork Skills and Plugins Vesa Juvonen - Copilot UX Components: From AI Chat to Interactive Business Applications – Sales Pipeline in Action 📞 & 📺 Join the Microsoft Teams meeting live at https://aka.ms/community/ms-speakers-call-join 🗓️ Download recurrent invite for this weekly call from https://aka.ms/community/ms-speakers-call-invite 👋 See you in the call! 💡 Building something cool for Copilot, Microsoft 365 or Power Platform (Copilot Studio, SharePoint, Power Apps, etc)? We are always looking for presenters - Volunteer for a community call demo at https://aka.ms/community/request/demo 📖 Resources: Previous community call recordings and demos from the Microsoft Community Learning YouTube channel at https://aka.ms/community/youtube Microsoft 365 & Power Platform samples from Microsoft and community - https://aka.ms/community/samples Microsoft 365 & Power Platform community details - https://aka.ms/community/home 🧡 Sharing is caring!Feature Request: Language-Based Font Categorization (Word, PowerPoint, & Microsoft 365 Apps)
Dear Microsoft Office Team, I am a regular user of Microsoft 365 applications, and I truly appreciate the continuous improvements made to the software. I would like to suggest a feature enhancement that would significantly improve the workflow for users working with multi-language documents and presentations across all design-dependent Microsoft apps (such as Word and PowerPoint): Categorized and language-separated font drop-down menus. Currently, when dealing with a large library of installed fonts, the font list mixes all languages together (Latin, Arabic, and other scripts). This makes it extremely difficult to compare font styles quickly, As a graphic designer, this issue is incredibly frustrating; when comparing fonts in programs like Word or PowerPoint, users are forced to constantly scroll up and down, often losing track of the font they liked. Personally, this leads me to either write down the names of the fonts on a separate sheet of paper or repeatedly type out the same sentence—applying a different font to each version—just so I can compare them side by side. My suggestion is to: Provide a clean, structured view where users can easily browse and compare font styles within the same language family without scrolling through long mixed list. Group fonts by language/script categories (e.g., all Arabic fonts grouped together, all English/Latin fonts grouped together, and so on). Extend this feature across all Office apps that rely heavily on typography and design (Word, PowerPoint, etc.). This feature would save an immense amount of time, reduce friction in document/presentation design, and elevate the overall user experience—much like how professional design software handles typography. Thank you for your time, consideration, and dedication to making Microsoft 365 better for everyone. Best regards, MINA-eNjOy
forms family acoount not sycing and caping at 200 responses
so i talked to miscorosft 2 days they sent me here, im ASD and frustarted and disregulated as to lack of support. I have a family account and my form caped at 200 responeses, and it should cap at 1000 responses, i cant create new form or link i need that one working. In my account in forms, it says buy microsoft365, but i already have it, and when i go to click it says im part of a family. there is some kinda disconnect. the form is live i been yelled at 2 days as ppl can not use it. someone please help and advise mePartner Blog | From Copilot adoption to agent-powered growth
A successful Copilot trial opens the door to a much bigger customer conversation and a bigger role for partners. Once users experience the value of AI in their daily work, partners can guide customers to extend that value across teams, workflows, and business processes while maintaining the security, governance, and cost controls needed to scale. In my recent post, From AI curiosity to Copilot adoption in 30 Days, I introduced how Cloud Solution Provider (CSP) partners can use a guided, 25-user trial to bring Microsoft 365 Copilot Business to small and medium-sized business (SMB) customers. That initial experience creates momentum, but sustaining it requires a structured approach to adoption, governance, and expansion. The opportunity is growing with the new Copilot, which brings Home, Code, and Autopilot together in one connected experience. Combined with a commercial model that supports subscriptions and usage-based billing, these advances create new ways for customers to move from AI assistance to delegated work and agent-powered business processes. For partners, this expands opportunities across the customer lifecycle, from guiding adoption and securing environments to developing agents, managing AI consumption, and delivering ongoing services. The key is connecting these capabilities into a repeatable practice that evolves alongside customer needs. Build on the momentum of Copilot in 30 The first 30 days give customers a practical foundation for working with AI. Through Copilot in 30, users explore how Microsoft 365 Copilot Business can improve everyday productivity across Outlook, Teams, Word, Excel, and PowerPoint before progressing to agents and more advanced scenarios. The Copilot Success Planner gives partners a structured way to guide this experience. It creates personalized learning plans for the 25 trial users, along with a roadmap for the customer sponsor. The guided journey builds skills progressively. If the sponsor enables Copilot Cowork, Weeks 3 and 4 add Cowork prompts that introduce the possibilities of delegated work. At the end of the trial, partners can use the sponsor's Day 30 value readout to identify where Copilot delivered results, which users and teams are ready to expand, and where additional capabilities could create business value. That conversation now has a broader destination. With the new Copilot, customers can move through connected experiences: Home brings Chat, Copilot Cowork, and Office together, so users can ask questions, create content, and delegate more complex work. Code extends AI-powered solution development, so users can turn natural-language ideas into apps, dashboards, automations, and workflows. Autopilot introduces a persistent, proactive personal agent designed to keep work moving within organizational permissions. Home and Code are rolling out through the Frontier program, and Autopilot is in private preview. They expand what customers can explore as their AI maturity grows, building on the foundation of everyday Copilot adoption. For partners, the next step is to turn early success into a longer-term customer roadmap. The Microsoft 365 Copilot + Agents SMB Guided Experience (download kit) provides a ready-to-deliver, 90-minute engagement to reinforce value, explore new scenarios, and guide the transition toward broader adoption. Continue reading here
