AI Didn’t Remove Programming – It Lowered the Bar

One of the most dangerous misunderstandings I hear is:
“AI means we don’t need programming anymore.”

The opposite is true.

We need more programming literacy—just a different kind.

AI doesn’t replace logic, structure, or clarity. It amplifies them. When an AI tool “writes code” for you, what it’s really doing is translating your intent into something executable. If your intent is vague, messy, or logically broken, the output will be too.

MSPs already see this in practice:

A poorly described Power Automate flow that works once and then quietly breaks.
An AI-generated script that technically runs but makes unsafe assumptions.
A Copilot prompt that looks clever but produces useless business output.

The common issue isn’t the tool. It’s the thinking behind the instructions.

Understanding basic concepts—inputs, outputs, conditions, loops, exceptions—has never been more important. The difference now is you don’t need to memorise syntax. You need to think clearly and explain cleanly.

This Is a Business Advantage, Not a Technical Party Trick

Here’s where many MSPs miss the opportunity.

They see AI-assisted “programming” as something clever techs play with internally. In reality, it’s fast becoming a deliverable business capability.

Think about your SMB clients:

They know their processes are inefficient.
They can explain what they want, but not how to build it.
They don’t want a six‑month dev project for a simple workflow problem.

An MSP that can sit with a client, map a process in plain English, and turn it into an automated solution is no longer just “support”. You’re helping redesign how the business operates.

And the simplicity is the point.

A one‑page English description that becomes:

A ticket triage workflow
An onboarding checklist generator
A management report assembler
A light internal chatbot using their own documents

None of that needs hardcore development skills anymore—but all of it still needs structured thinking.

Your Team Doesn’t Need Coding Skills – They Need Programming Awareness

This is where MSP leaders need to be deliberate.

You don’t suddenly need Python experts across your service desk. What you do need is:

Staff who can break problems into steps
People who can explain outcomes unambiguously
A shared understanding of how logic flows

If your team can already document SOPs well, they are halfway there.

I’ve seen MSPs get real value by:

Treating AI prompts like mini specifications, not chat questions
Reviewing AI-generated automations as a team, not blindly deploying them
Teaching junior staff how to describe a problem, not just which tool to click

Those are capability investments, not tool training.

The MSPs Who Win Will Treat This as a Core Skill

We’ve crossed a line. Programming is no longer gated by language barriers—it’s gated by thinking quality.

That changes what “technical literacy” means for MSPs.

The firms that thrive over the next few years won’t be the ones chasing every new AI tool. They’ll be the ones that:

Build strong internal habits around logical thinking
Help clients translate business problems into clear instructions
Package simple automation as repeatable, billable outcomes

If English is now the language of code, the question is simple:

Are you teaching your people how to speak it clearly—or assuming the tools will do that for them?

That’s a strategic choice every MSP leader needs to make, sooner rather than later.

Step-by-Step Program to Achieve Priority #6 with Microsoft 365 Business Premium

This is part of a series on MSP priorities for 2026.

Driving Efficiency with Process Automation – Program Overview: To rapidly streamline SMB operations, MSPs should implement a structured program focusing on quick automation wins, gradual scaling, and strong governance. The plan below leverages Microsoft 365 Business Premium tools (Power Automate, Teams, SharePoint, Copilot, etc.) to automate high-volume, repetitive tasks and continuously improve processes while maintaining security and compliance.

Step-by-Step Program for MSPs (SMB Clients): The table below outlines each step, its purpose, tools, timeline, and key considerations:

Step Name	Description (What MSP does)	Tools Used (M365 Business Premium)	Est. Timeline	Key Considerations (Resources & Governance)
1. Process Discovery & Prioritization	Conduct an automation audit with client stakeholders. Identify repetitive, high-friction processes (e.g. data entry, approvals, reporting) and rank them by impact and feasibility [blog.sourcepass.com]. Produce a roadmap focusing on one or two quick-win processes first.	Workshops; Microsoft Forms/Lists to capture process info; Planner for backlog prioritization.	~2–4 weeks (Month 1)	Resources: Client process owners & MSP business analyst collaborate. Considerations: Ensure leadership buy-in on target processes and confirm any compliance requirements (e.g. data privacy) before automation.
2. Solution Design & Pilot Build	For the top priority process, design the workflow and choose the appropriate automation approach. Configure a pilot solution – e.g. build a Power Automate flow or simple Power App – addressing the selected task. Incorporate Copilot or AI if it adds value (e.g. use Copilot Studio to create an AI that handles unstructured inputs or generates content as part of the process) [blog.sourcepass.com], [blog.sourcepass.com]. Test the pilot in a controlled setting with sample data.	Power Automate (cloud flows or RPA desktop flows) for workflow logic; Power Apps for a custom input form (if needed); Teams (Copilot Chat) or Copilot Studio to design AI-assisted steps (optional); SharePoint (test data lists or library).	~4–6 weeks (Month 2)	Resources: MSP Power Platform developer (or skilled engineer) builds the pilot; client subject-matter experts provide feedback. Considerations: Adhere to security best practices – e.g. use least-privilege accounts for automation, and ensure data sensitivity labels/permissions are respected during design [blog.sourcepass.com]. Plan for pilot success metrics (e.g. time saved, error reduction).
3. Pilot Deployment & Evaluation	Deploy the pilot automation in the client’s live environment for a small user group or single department. Train those users on the new workflow (e.g. how approvals now come via Teams, or how a bot assists them). Monitor the results closely: verify the automation is running correctly, gather user feedback, and measure performance against baselines (e.g. process cycle time, error rates) [blog.sourcepass.com]. Evaluate ROI and satisfaction to decide on broader rollout.	Microsoft Teams (pilot users receive workflow notifications/approvals in Teams); SharePoint/OneDrive (live data storage); Power BI or Excel for tracking metrics (optional).	~2–4 weeks (Month 3)	Resources: MSP consultant & client IT lead to support pilot users; helpdesk ready for issues. Considerations: Implement initial governance checks – e.g. review audit logs of the flow, ensure compliance with data policies during pilot. Collect success data (e.g. “Process X now 50% faster”) to secure full rollout approval [cmitsolutions.com].
4. Broad Rollout & Expansion	With pilot success, roll out the automation to all relevant users or across the organization. Integrate the solution with additional systems if needed (e.g. link to email, CRM, or third-party apps via connectors). In parallel, expand automation to the next priority processes on the roadmap [cmitsolutions.com]. Use lessons from the pilot to accelerate development of new workflows (leveraging templates and proven patterns). Conduct user training and change management for each new automation to ensure adoption.	Power Automate (additional flows or RPA bots for new processes); Teams and Outlook (wider notification channels); Connectors for third-party apps (if automating beyond Microsoft ecosystem); possibly Power Virtual Agents (for chatbot interfaces to processes).	Phase-wise over ~3–6 months (Months 3–6+ for multiple automations)	Resources: Additional MSP engineering time for each new process; client department champions to help roll out and train colleagues. Considerations: Stagger deployments to manage change – e.g. automate one process at a time. Verify licensing (Business Premium covers standard automation; ensure any premium connectors or AI features are licensed appropriately). Continuously update documentation for each automated workflow. Maintain alignment with security policies for new processes (e.g. if automating finance tasks, involve compliance officer in design).
5. Ongoing Governance & Optimization	Establish a governance framework to sustain and improve the automation portfolio. Assign ownership for each automated workflow (who will update it when business processes change). Set up monitoring and alerts for failures or exceptions. Enforce security and compliance standards: e.g. use Azure AD role-based access control for connectors, regularly review permissions of automation accounts, and ensure data handling meets regulations. Optimize continuously by reviewing performance metrics and user feedback on a scheduled basis (e.g. quarterly). Identify new automation opportunities as the client’s needs evolve, and fold them into the program.	Power Platform Admin Center (governance of environments, data loss prevention (DLP) policies); Azure AD / Entra ID (manage service accounts and roles); Microsoft 365 Admin & Security Centers (monitor audit logs, compliance status); Power BI dashboards (ongoing KPI tracking).	Ongoing (governance reviews monthly; new enhancements each quarter)	Resources: MSP offers managed services for automation – providing a dedicated advisor for upkeep. Considerations: Treat governance as “business-as-usual”: implement policies for change control (e.g. approval required to publish new automation), and training programs to keep users and admins up to date. Ensure measurable outcomes are reported to client leadership regularly (e.g. quarterly business reviews highlighting time saved or error reduction) to demonstrate value and adjust the roadmap.

Implementation Timeline: This program is typically executed in phases over ~3–6 months for initial automations. For example, within 90 days an MSP can complete assessment, deliver one or two automation solutions, and have a roadmap for subsequent projects. Quick wins (like automating backups or simple approvals) are done first to reduce risk and show impact early, while more complex workflows are scheduled for later phases. The timeline can be adjusted based on the client’s size and readiness. [cmitsolutions.com]

Resource Requirements & Governance: Throughout the program, MSPs should plan for cross-functional resources – e.g. business analysts (to map processes), Power Platform developers, and cloud security experts. SMB client participation is vital, including process owners and IT admins to champion the changes. Leverage Microsoft 365 Business Premium’s integrated security (Azure AD identity, Microsoft Purview compliance, Defender) to build trust in the automation. Crucially, embed governance as a continuous thread: set clear data access boundaries, maintain an inventory of automations, and provide user training and support as new workflows roll out. This ensures that efficiency gains from automation are realized safely and sustainably – achieving the outcomes of reduced manual effort, faster service delivery, and higher consistency that Step Six outlines. [itarian.com], [cmitsolutions.com]

Need to Know podcast–Episode 350

In Episode 350 of the CIAOPS “Need to Know” podcast, along with the latest news from the Microsoft Cloud, we explore how Microsoft Power Pages is revolutionising web development for SMBs. Learn how this low-code platform enables businesses to build secure, scalable portals—without needing full-stack developers. From customer support portals to partner onboarding, discover real-world use cases, a step-by-step guide to building your first portal, and how Managed Service Providers (MSPs) can offer Power Pages as a service. This episode is a must-listen for IT professionals, MSPs, and business leaders driving digital transformation.

Brought to you by www.ciaopspatron.com

you can listen directly to this episode at:

https://ciaops.podbean.com/e/episode-350-power-up/

Subscribe via iTunes at:

https://itunes.apple.com/au/podcast/ciaops-need-to-know-podcasts/id406891445?mt=2

or Spotify:

https://open.spotify.com/show/7ejj00cOuw8977GnnE2lPb

Don’t forget to give the show a rating as well as send me any feedback or suggestions you may have for the show.

Resources

CIAOPS Need to Know podcast – CIAOPS – Need to Know podcasts | CIAOPS

X – https://www.twitter.com/directorcia

Join my Teams shared channel – Join my Teams Shared Channel – CIAOPS

CIAOPS Merch store – CIAOPS

Become a CIAOPS Patron – CIAOPS Patron

CIAOPS Blog – CIAOPS – Information about SharePoint, Microsoft 365, Azure, Mobility and Productivity from the Computer Information Agency

CIAOPS Brief – CIA Brief – CIAOPS

CIAOPS Labs – CIAOPS Labs – The Special Activities Division of the CIAOPS

Support CIAOPS – https://ko-fi.com/ciaops

Get your M365 questions answered via email

Show Notes

Getting started with the Microsoft Power Platform

The goal is to empower you (and your colleagues) to build solutions *without* necessarily needing deep coding expertise, focusing on productivity boosts and automating those repetitive tasks.

What is the Power Platform?

Think of it as a suite of low-code/no-code tools that work seamlessly with Microsoft 365 (and many other services) to:

Power Apps: Build custom applications (mobile or web) for specific tasks or processes.
Power Automate: Automate workflows and repetitive tasks between different apps and services.
Power BI: Analyze data and create interactive dashboards and reports (often used alongside the others, but slightly different focus).
Power Virtual Agents: Build intelligent chatbots without code.
(Underlying) Dataverse: A secure, scalable data platform to store and manage data used by your Power Platform solutions (think of it as a sophisticated database optimized for business apps).

For quick and easy productivity gains and automation, we’ll primarily focus on Power Apps and Power Automate.

Prerequisites & Access

Microsoft 365 License: Most standard Microsoft 365 Business or Enterprise licenses (like E3, E5, Business Standard, Business Premium) include foundational Power Platform capabilities. This typically covers:
- Running apps.
- Creating flows with Standard connectors (like SharePoint, Outlook, Teams, OneDrive, Forms, Excel Online).
- Limited Dataverse usage.
- Important Note: Using Premium connectors (like SQL Server, Salesforce, custom APIs), AI Builder features, RPA (Robotic Process Automation), or extensive Dataverse capacity often requires additional standalone Power Apps or Power Automate licenses. Start with what’s included first!
Accessing the Tools:
- Go to Office.com and sign in with your work account.
- Click the App Launcher (the “waffle” icon, 9 dots) in the top-left corner.
- You should see icons for Power Apps and Power Automate. If not, click “All apps”.
- Alternatively, go directly to:
  - make.powerapps.com for Power Apps
  - make.powerautomate.com (or flow.microsoft.com) for Power Automate

Getting Started: The Strategy

The key is to start small and focus on a specific pain point. Don’t try to boil the ocean.

Identify a Bottleneck or Repetitive Task: What’s something you or your team does regularly that is manual, time-consuming, or prone to errors?
- Examples: Manually copying data from an email into a spreadsheet, chasing people for approvals, collecting information via long email chains, tracking simple requests on paper or a shared doc.
Choose the Right Tool (Initially):
- Need to automate a process that runs in the background? (e.g., save email attachments, notify a team when a file is updated, request approval) -> Power Automate is likely your best bet.
- Need a user interface to interact with data or kick off a process? (e.g., a simple form to submit requests, a way to view and update items in a list, a checklist app) -> Power Apps is probably the way to go. Often, Power Apps and Power Automate work together.
Leverage Templates: This is the ABSOLUTE EASIEST way to start. Both Power Apps and Power Automate have extensive template galleries based on common scenarios.
Connect Your M365 Services: The real power comes from connecting the tools you already use (Outlook, Teams, SharePoint, OneDrive, Forms, Planner, etc.).
Build, Test, Iterate: Your first attempt won’t be perfect. Build something simple, test it, get feedback, and refine it.

Detailed Steps with Examples:

Scenario 1: Automating Email Attachments to OneDrive (Using Power Automate)

Pain Point: You receive regular reports via email from a specific sender and have to manually save the attachments to a designated OneDrive folder.
Tool: Power Automate
Steps:
1. Go to make.powerautomate.com.
2. On the left menu, click Templates.
3. Search for “Save email attachments to OneDrive”. You’ll find several variations. Select one like “Save Office 365 email attachments to a specified OneDrive for Business folder”.
4. Review the flow description and the connections it needs (Office 365 Outlook, OneDrive for Business).
5. Click Continue. Power Automate will check if you’re already signed into these services or prompt you to sign in.
6. Configure the Trigger: The template likely starts with the “When a new email arrives (V3)” trigger. You need to customize it:
  - Folder: Usually Inbox.
  - From: Enter the specific email address of the sender.
  - Include Attachments: Set to Yes.
  - Subject Filter: (Optional but recommended) Enter keywords from the subject line to be more specific (e.g., “Weekly Report”).
7. Configure the Action(s): The template will have actions like “Apply to each” (to handle multiple attachments) and “Create file” (for OneDrive).
  - In the “Create file” action:
    - Folder Path: Click the folder icon and navigate to the exact OneDrive folder where you want to save the files.
    - File Name: The template usually pre-fills this with Attachments Name (dynamic content from the trigger). This is good.
    - File Content: The template usually pre-fills this with Attachments Content. This is also good.
8. Save the flow.
9. Test the flow. You can use the “Test” button in the top-right. Choose “Manually” and then trigger the flow by having an email sent that matches your criteria (or use a recent email if available via automatic testing).
10. Turn it On: Once saved, the flow is active and will run automatically whenever a new email matching your criteria arrives.
Productivity Gain: Saves you minutes every time that email arrives, reduces the chance of forgetting, and keeps files organized automatically.

Scenario 2: Creating a Simple Request Form/Tracker (Using Power Apps & SharePoint)

Pain Point: Your team uses email or chat to request small IT support items, making them hard to track and manage.
Tools: SharePoint (for data storage), Power Apps (for the user interface)
Steps:
1. Create a SharePoint List:
  - Go to your team’s SharePoint site (or create a new one).
  - Click + New > List.
  - Choose Blank list. Name it something like “IT Support Requests”.
  - Add columns relevant to the request:
    - Title (Rename to “Short Description” – required by default)
    - Requester (Person or Group column, default to current user)
    - RequestDetails (Multiple lines of text)
    - Urgency (Choice column: High, Medium, Low)
    - Status (Choice column: New, In Progress, Completed, Cancelled – default to ‘New’)
    - AssignedTo (Person or Group column – optional initially)
    - CompletionDate (Date and Time column – optional)
2. Create the Power App:
  - Go to make.powerapps.com.
  - Click Create > SharePoint.
  - It will ask you to select or enter a SharePoint site URL. Find your site.
  - Select the “IT Support Requests” list you just created.
  - Click Create.
3. Automatic App Generation: Power Apps will automatically generate a basic 3-screen app (Browse, View Details, Edit/Create New) based on your SharePoint list columns!
4. Customize (Optional but Recommended):
  - Browse Screen: Select the gallery (the list of items). In the right-hand pane (or top formula bar), you can change which fields are displayed. Maybe show Title, Requester, and Status.
  - Edit/New Screen: Select the form. In the right-hand pane, click “Edit fields”. You can reorder fields, change control types (e.g., make RequestDetails bigger), or remove fields you don’t want users filling in (like AssignedTo if only IT assigns). Set the default value for Status to “New”.
  - Theme/Colors: Use the “Theme” option on the Home tab to quickly change the look and feel.
5. Save the app (give it a meaningful name like “IT Request App”).
6. Publish the app.
7. Share the app:
  - Click Share (top right or from the app list).
  - Enter the names or email addresses of the colleagues who need to submit requests.
  - Crucially: Make sure they also have permission to access the underlying SharePoint list! Grant them “Contribute” access to the list itself in SharePoint.
  - Decide if you want to send an email invitation.
8. Accessing the App: Users can access the app via the Power Apps mobile client, directly from the web link you share, or you can even embed it within a SharePoint page or Microsoft Teams tab for easier access.
Productivity Gain: Centralized request tracking, standardized information collection, clear status visibility, replaces messy email/chat trails.

Further Steps & Learning:

Explore More Templates: Both Power Apps and Power Automate have hundreds. Browse them for inspiration.
Learn about Connectors: Understand the difference between Standard (included with M365) and Premium (require extra licenses). Explore the vast list of available connectors.
Combine Power Apps and Power Automate:
- Trigger a Power Automate flow from a Power App button (e.g., when a new IT request is submitted in the app, trigger a flow to post a notification in a Teams channel).
- Use Power Automate to update data that your Power App displays.
Microsoft Learn: This is your BEST resource for structured learning. Search for Power Apps and Power Automate paths and modules – many are beginner-focused. (learn.microsoft.com)
Power Platform Community: Ask questions, see what others are building. (powerusers.microsoft.com)
Experiment: The best way to learn is by doing. Pick another small task and try to build a solution! Don’t be afraid to try things out in the editor.

Key Mindset:

Low-Code, Not No-Effort: While you don’t need traditional coding, you do need to think logically about process steps (for Automate) and user interface design (for Apps).
Iterative Improvement: Your first version is just the start. Use it, get feedback, and make it better over time.
Focus on Value: Prioritize automating tasks or building apps that provide the most significant time savings or process improvements first.

By starting small, using templates, and focusing on your existing M365 tools, you can quickly begin leveraging the Power Platform to make a real difference in your daily productivity and reduce manual work. Good luck!

Accessing Azure Key Vault via Power Automate

In a previous article:

Adding a secret to an Azure Key Vault

I showed how a secure credential could be saved to an Azure Key Vault and then retrieved either from the browser, or PowerShell. You can however, also retrieve a secret using Power Automate.

You can see I have the same ‘super secret’ password stored in the Azure Key Vault above.

The Azure Key Vault connector in Power Automate is a premium connector which means you’ll either need an advanced Power Platform license or you’ll need to set up a

Power Platform PAYG configuration

which is probably the more cost effective approach.

You’ll firstly need to login to your Power Platform environment and select Connectors from the menu on the left as shown above. In here look for the Azure Key Vault connector. If it is not there select the +New connector from the menu at the top.

Search for key vault in the top right and then select Azure Key Vault as shown above. You will note that this connector is a Premium connector as highlighted earlier.

Enter the vault name and select Create.

You should now see the connector displayed in the list as shown above.

If you select this connector you will see additional information and the connection Status as well. Icons on the menu bar at the top that allow you to maintain this connector if needed.

Create a new flow and add a new step. Search for key vault as shown and select Get Secret as the action below as shown above.

If you pull down the Name of the secret field you should see your secret name previously created in the Azure Key Vault as shown above, which you can select.

Complete your flow. Here I’m just going to output the value of the secret (i.e. the password) to a Microsoft Team channel.

If you now run the flow you see that it succeeds.

You should also see the output of the secret (i.e. here the password) stored in the Azure Key Vault displayed as shown above.

Another advantage of using an Azure Key Vault is that you can use it a variety of tools such as PowerShell and Power Automate as I have shown here. This means that the credentials stay secure and can still be accessed via your automation process.

Announcing the CIAOPS Power Automate online course

I have just released my new Introduction to Power Automate course which you can find here:

https://www.ciaopsacademy.com/p/introduction-to-power-automate

The course is designed to give you a kick start into the world of automation with Microsoft 365. You’ll learn what Power Automate and Flows are including how to create the different types as well as use connectors to work with data from a variety of sources.

Inside you’ll find a variety of resources including video tutorials, web references, quizzes, examples and more. Upon completion, you will have the confidence to start automating many processes in your business.

Once you get started with Power Automate you’ll be amazed at how much time you’ll save, all using the tools that come with Microsoft 365.

Start here. Start today. And get more time in your day.

Power Automate Email Arrive action file size only 4 bytes

If you create a Power Automate with a trigger of When a new email arrives (V3) and you want to work with attachments in your Flow, ensure you select the Show advanced options as shown above.

If you don’t you’ll end up with saved attachments of only 4 bytes in size as shown above as by default the action doesn’t include attachments.

To work with attachments in your Flow, ensure the Include Attachments option is set to Yes as shown above. Then you’ll be able to do things like save the whole attachment to OneDrive for Business.

Adoption with fun and OpenAI

I’ve detailed how to use an API with Power Automate to inject some engaging content automatically into Microsoft Teams.

Adoption with fund and astronomy

Thanks to API’s I want to extend this to use OpenAI and ChatGPT.

What I want to achieve is to ask a question of ChatGPT via an API everyday something like this:

“Tell me about 1 May as a list”

When I do this interactively at chat.openai.com I see:

I now want something like that to appear in Microsoft Teams daily for each day.

You’ll need to head over to OpenAI and get an API key. Here’s how to do that:

How to get an OpenAI API key in just 5 easy steps

I’d also suggest signing up for an OpenAI API subscription if you want to continue using this service. Here’s an idea of the costs.

Create a new Scheduled cloud flow. Don’t forget to change the repeat option to 1 day typically.

Add the Current Time action.

Add the Convert time zone action to get the time in your location. Set the format string to Month/day pattern (i.e. May 1).

Add the HTTP action. Remember, this is a Premium connector. Set teh following options here:

Method = POST

URI = https://api.openai.com/v1/chat/completions

Accept = application/xml

Content-Type = application/json

Authorization = Bearer (your OpenAI API key)

Body:

{
   “model”: “gpt-3.5-turbo”,
   “max_tokens”: 2000,
   “temperature”: 0,
   “messages”: [
     {
       “role”: “user”,
       “content”: “Tell me about @{body(‘Convert_time_zone’)} as a list”
     }
   ]
}

Ensure you double check all these settings as it is easy to make a mistake.

Add the Parse JSON action.

I’ve put the JSON schema you need here:

https://github.com/directorcia/general/blob/master/Power%20Platform/OpenAI/JSON-for-GPT

Add the Initialize variable action. We need to extract the returned text and format it so it will display in Teams. That means replacing the ‘/n’ string ‘<br>’. That can be done via this expression:

replace(body(‘Parse_JSON’)?[‘choices’][0]?[‘message’]?[‘content’],’/n’,’<br>’)

NOTE: if you copy and paste this expression and receive an error when you try and save it, you’ll most likely have to change the apostrophe from ‘ to ‘. It’s subtle, but you need to use the one to the left of the ENTER key on most keyboards to get it to work in Power Automate.

Finally add the Post message in chat or channel action.

Ensure you swap to the HTML editor using the </> item in the top right of the message as shown above.

Format the message the way you want to and insert variable created previously as shown.

When the Flow executes the output should look something like the above.

Note that GPT isn’t always right! You can also change the AI models if you wish, but remember they have different prices.

Typically, I’d suggest you run this Flow once a day to promote more engagement in your Microsoft Team. Better yet, you can show everyone how you are integrating AI into Teams. Yet another point of engagement in your Microsoft Team and perhaps a way to spark ideas for how you can expand the use of OpenAI in yoru business.