> For the complete documentation index, see [llms.txt](https://docs.rewst.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rewst.help/updates/roc-open-mics/roc-open-mics-north-america/2025-roc-open-mics/march-14-2025-an-m365-special-workflows-that-focus-on-microsoft-365.md).

# March 14, 2025: An M365 Special! Workflows that Focus on Microsoft 365!

### **Join Live!**

Join us live every Friday at 3 pm EST!

[Download the Calendar Invite here](https://engine.rewst.io/webhooks/custom/trigger/02eb02e2-1177-43d9-9e13-8547414979fc/c47fdd7f-4075-47a8-ba92-94e790e67c06?request_type=open_mic_link&)!

## Open Mic Video Recording

{% embed url="<https://youtu.be/J1ArqY3X2n8>" %}

### Contents of the Recording:

* 🎙️ Aaron returns after a short break, reminding MSPs about Flow, the automation conference, and encouraging participation in Discord for questions and collaboration.
* 🚀 Frank shares performance improvements, bug fixes, and new features, including a Stripe integration, Robo-Ry upgrades, and a new dashboard widget.
* 🛒 JP introduces a Microsoft 365 Subscription Renewal Alerts crate and upcoming reports for inactive RMM agents and AV disparities.
* 🎓 Brandon announces training schedule changes, certification achievements, and documentation updates.
* 🎥 George reminds the community to contribute short Rewst 101 videos for new users.
* 📊 Austin showcases how his MSP replaced a third-party billing tool with Rewst automation, using App Builder for internal workflows.
* 🔐 Linda presents a ConnectWise MFA audit workflow that saves hours by automatically generating a compliance report.
* 📅 Joe automates scheduling meetings via Microsoft Bookings, reducing costs by replacing a third-party tool.
* 🤖 Brett and others discuss integrating Rewst with GitHub, Cursor, and CloudRadial for automation efficiency.
* 📜 Kelvin provides insights on Microsoft's crackdown on under-licensed tenants and the importance of compliance.
* 👋 Aaron thanks presenters, encourages more MSPs to demo their work, and closes out the session.

<details>

<summary><strong>How to Get Help</strong></summary>

* 💬 Chat (Discord): [https://discord.gg/rewst​​](https://discord.gg/rewst%E2%80%8B%E2%80%8B)
  * Private #{{ msp }} channel
  * \#the-kewp
* 🎫 Submit Tickets to: <the_roc@rewst.io>
* 📝 Feature Request + Integration Requests: <https://rewst.canny.io/>

**CLUCK UNIVERSITY – REWST TRAINING:**

* 👨‍🏫 Live Instructor-Led Training: <https://calendly.com/cluck-u/>
* 🏁 Rewst Foundations Training: <https://docs.rewst.help/cluck-university/rewst-foundations-10x>
* ▶️ On-demand Videos: <https://docs.rewst.help/cluck-university/rewst-foundations-10x>

**DOCS:**

* 🥚 Rewst Docs: <https://docs.rewst.help>
* ⛩️ Jinja Docs: <https://jinja.palletsprojects.com/>

**KEY LINKS:**

* 📝 Feature Request + Integration Requests: <https://rewst.canny.io/>

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.rewst.help/updates/roc-open-mics/roc-open-mics-north-america/2025-roc-open-mics/march-14-2025-an-m365-special-workflows-that-focus-on-microsoft-365.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.