GitHub PowerShell Daily Trending

microsoft/hve-core

A refined collection of Hypervelocity Engineering components (instructions, prompts, agents, and skills) to start your project off right, or upgrade your existing projects to get the most out of all Copilots

title: HVE Core description: Hypervelocity Engineering prompt library for GitHub Copilot with constraint-based AI workflows and validated artifacts author: Microsoft ms.date: 2026-03-22 ms.topic: overview keywords:

hypervelocity engineering
prompt engineering
github copilot
ai workflows
custom agents
copilot instructions
rpi methodology estimated_reading_time: 3

Hypervelocity Engineering (HVE) Core gives you specialized agents, auto-applied coding instructions, reusable prompts, and validated skills for GitHub Copilot. Turn Copilot into a constraint-based engineering workflow that scales from solo developers to enterprise teams.

Tip

Install from the VS Code Marketplace in under 30 seconds. See the Installation Guide for all options.

Quick Start

Install the HVE Core extension from the VS Code Marketplace.
Open any project and launch GitHub Copilot Chat (Ctrl+Alt+I).
Select an agent from the picker (try rpi-agent, task-researcher, or memory) and start a conversation.

That's it. Agents, instructions, and prompts activate automatically once the extension is installed.

Ready for more? Follow the Getting Started Guide.

Choose Your Extension

Two VS Code extensions serve different needs:

Extension	What it includes	Best for
HVE Core All	Every collection: all agents, prompts, instructions, and skills	Individual developers and teams that want the full library
HVE Installer	Selective installation of specific collections	Teams that want to pick only the collections relevant to their workflow

Not sure which to choose? Start with HVE Core All. You can switch to HVE Installer later if you need finer control over which collections are active. See the Collections Overview for a comparison of all available bundles.

What's Included

Component	Count	Description	Documentation
Agents	49	Specialized AI assistants for research, planning, and implementation	Agents
Instructions	102	Repository-specific coding guidelines applied automatically	Instructions
Prompts	63	Reusable templates for common tasks like commits and PRs	Prompts
Skills	11	Self-contained packages with cross-platform scripts and guidance	Skills
Scripts	N/A	Validation tools for linting, security, and quality	Scripts

Documentation

Full documentation is available at https://microsoft.github.io/hve-core/.

Guide	Description
Getting Started	Setup and first workflow tutorial
Collections	Available bundles and selection guide
RPI Workflow	Deep dive into Research, Plan, Implement
Contributing	Create custom agents, instructions, and prompts
Agents Reference	All available agents
Instructions Reference	All coding instructions
AI Artifacts Architecture	Prompt engineering framework and artifact types
Validation Standards	CI/CD validation pipeline and quality gates

Label Management

Repository labels are declared in .github/labels.yml and synced automatically by the Label Sync workflow on push to main or via manual workflow_dispatch.

Task	How
Add a label	Add an entry with `name`, `color` (bare hex, no `#`), and `description` to `.github/labels.yml`, then push to `main`
Update a label	Edit the existing entry's `color` or `description`
Rename a label	Add an `aliases` array under the new canonical name listing the old name; the sync migrates existing assignments automatically
Delete a label	Remove it manually in the GitHub Labels UI. Deleting an entry from the file does not delete it from GitHub (the workflow runs in additive mode)

Contributing

We appreciate contributions! Whether you're fixing typos or adding new components:

Read our Contributing Guide.
Check out open issues.
Join the discussion.

Responsible AI

Microsoft encourages customers to review its Responsible AI Standard when developing AI-enabled systems to ensure ethical, safe, and inclusive AI practices. Learn more at Microsoft's Responsible AI.

Legal

This project is licensed under the MIT License.

Licensing

Most content in this repository is covered by the MIT License. Certain skill content derived from OWASP Foundation publications is licensed under CC BY-SA 4.0. Each affected skill identifies its license in frontmatter and includes a Third-Party Attribution section. See THIRD-PARTY-NOTICES for full details.

See SECURITY.md for the security policy and vulnerability reporting.

See GOVERNANCE.md for the project governance model.

Trademark Notice

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.

🤖 Crafted with precision by ✨Copilot following brilliant human instruction, then carefully refined by our team of discerning human reviewers.

psmux/psmux

Tmux on Windows Powershell - tmux for PowerShell, Windows Terminal, cmd.exe. Includes psmux, pmux, and tmux commands. This is native Powershell Tmux designed for Windows in Rust 🦀

╔═══════════════════════════════════════════════════════════╗
║   ██████╗ ███████╗███╗   ███╗██╗   ██╗██╗  ██╗            ║
║   ██╔══██╗██╔════╝████╗ ████║██║   ██║╚██╗██╔╝            ║
║   ██████╔╝███████╗██╔████╔██║██║   ██║ ╚███╔╝             ║
║   ██╔═══╝ ╚════██║██║╚██╔╝██║██║   ██║ ██╔██╗             ║
║   ██║     ███████║██║ ╚═╝ ██║╚██████╔╝██╔╝ ██╗            ║
║   ╚═╝     ╚══════╝╚═╝     ╚═╝ ╚═════╝ ╚═╝  ╚═╝            ║
║     Born in PowerShell. Made in Rust. 🦀                 ║
║          Terminal Multiplexer for Windows                 ║
╚═══════════════════════════════════════════════════════════╝

The native Windows tmux. Born in PowerShell, made in Rust.
Full mouse support · tmux themes · tmux config · 83 commands · blazing fast

Install · Usage · Claude Code · Features · Compatibility · Performance · Plugins · Keys · Scripting · Config · Mouse/SSH · FAQ · Related Projects

psmux

The real tmux for Windows. Not a port, not a wrapper, not a workaround.

psmux is a native Windows terminal multiplexer built from the ground up in Rust. It uses Windows ConPTY directly, speaks the tmux command language, reads your .tmux.conf, and supports tmux themes. All without WSL, Cygwin, or MSYS2.

💡 Tip: psmux ships with tmux and pmux aliases. Just type tmux and it works!

👀 On Windows 👇

Installation

Using WinGet

winget install psmux

Using Cargo

cargo install psmux

This installs psmux, pmux, and tmux binaries to your Cargo bin directory.

Using Scoop

scoop bucket add psmux https://github.com/psmux/scoop-psmux
scoop install psmux

Using Chocolatey

choco install psmux

From GitHub Releases

Download the latest .zip from GitHub Releases and add to your PATH.

From Source

git clone https://github.com/psmux/psmux.git
cd psmux
cargo build --release

Built binaries:

target\release\psmux.exe
target\release\pmux.exe
target\release\tmux.exe

Docker (build environment)

A ready-made Windows container with Rust + MSVC + SSH for building psmux:

cd docker
docker build -t psmux-dev .
docker run -d --name psmux-dev -p 127.0.0.1:2222:22 -e ADMIN_PASSWORD=YourPass123! psmux-dev
ssh ContainerAdministrator@localhost -p 2222

See docker/README.md for full details.

Requirements

Windows 10 or Windows 11
PowerShell 7+ (recommended) or cmd.exe
- Download PowerShell: winget install --id Microsoft.PowerShell
- Or visit: https://aka.ms/powershell

Why psmux?

If you've used tmux on Linux/macOS and wished you had something like it on Windows, this is it. Split panes, multiple windows, session persistence, full mouse support, tmux themes, 83 commands, 140+ format variables, 53 vim copy-mode keys. Your existing .tmux.conf works. Full details: docs/features.md · docs/compatibility.md

Usage

Use psmux, pmux, or tmux — they're identical:

psmux                        # Start a new session
psmux new-session -s work    # Named session
psmux ls                     # List sessions
psmux attach -t work         # Attach to a session
psmux --help                 # Show help

Claude Code Agent Teams

psmux has first-class support for Claude Code agent teams. When Claude Code runs inside a psmux session, teammate agents automatically spawn in separate tmux panes instead of running in-process.

psmux new-session -s work    # Start a psmux session
claude                       # Run Claude Code — agent teams just work

No extra configuration needed. Full guide: docs/claude-code.md

Documentation

Topic	Description
Features	Full feature list — mouse, copy mode, layouts, format engine
Compatibility	tmux command/config compatibility matrix
Performance	Benchmarks and optimization details
Key Bindings	Default keys and customization
Scripting	83 commands, hooks, targets, pipe-pane
Configuration	Config files, options, environment variables
Plugins & Themes	Plugin ecosystem — Catppuccin, Dracula, Nord, and more
Mouse Over SSH	SSH mouse support and Windows version requirements
Claude Code	Agent teams integration guide
FAQ	Common questions and answers

Related Projects

pstop _{htop for Windows — real-time system monitor with per-core CPU bars, tree view, 7 color schemes} `cargo install pstop`	psnet _{Real-time TUI network monitor — live speed graphs, connections, traffic log, packet sniffer} `cargo install psnet`
Tmux Plugin Panel _{TUI plugin & theme manager for tmux and psmux — browse, install, update from your terminal} `cargo install tmuxpanel`	OMP Manager _{Oh My Posh setup wizard — browse 100+ themes, install fonts, configure shells automatically} `cargo install omp-manager`

License

MIT

Contributing

Contributions welcome — bug reports, PRs, docs, and test scripts via GitHub Issues.

If psmux helps your Windows workflow, consider giving it a ⭐ on GitHub!

Star History

Made with ❤️ for PowerShell using Rust 🦀

Orange-Cyberdefense/GOAD

game of active directory

GOAD (v3)

🔖 Documentation : https://orange-cyberdefense.github.io/GOAD/

Description

GOAD is a pentest active directory LAB project. The purpose of this lab is to give pentesters a vulnerable Active directory environment ready to use to practice usual attack techniques.

Caution

This lab is extremely vulnerable, do not reuse recipe to build your environment and do not deploy this environment on internet without isolation (this is a recommendation, use it as your own risk).
This repository was build for pentest practice.

Licenses

This lab use free Windows VM only (180 days). After that delay enter a license on each server or rebuild all the lab (may be it's time for an update 😉)

Available labs

GOAD Lab family and extensions overview

GOAD : 5 vms, 2 forests, 3 domains (full goad lab)

GOAD-Light : 3 vms, 1 forest, 2 domains (smaller goad lab for those with a smaller pc)

MINILAB: 2 vms, 1 forest, 1 domain (basic lab with one DC (windows server 2019) and one Workstation (windows 10))
SCCM : 4 vms, 1 forest, 1 domain, with microsoft configuration manager installed

NHA : A challenge with 5 vms and 2 domains. no schema provided, you will have to find out how break it.

DRACARYS : A challenge with 3 vms and 1 domains. no schema provided, you will have to find out how break it.

microsoft/fabric-toolbox

Fabric toolbox is a repository of tools, accelerators, scripts, and samples to accelerate your success with Microsoft Fabric, brought to you by Fabric CAT.

Welcome to the Fabric Toolbox

Fabric toolbox is a repository of tools, accelerators, scripts, and samples to help you work with Microsoft Fabric. This repository is brought to you by the Fabric Customer Advisory Team (CAT) and will continue to grow as we develop new tools and accelerators.

These assets should be treated as examples that you can use to create the solutions that are appropriate for your use case. If you have any issues, please use the issues tab of this repository and we will work to address issues on a best effort basis.

Monitoring

$${\color{yellow}UPDATED!}$$ Fabric Cost Analysis (FCA)
$${\color{yellow}UPDATED!}$$ Fabric Unified Admin Monitoring (FUAM)
Fabric Platform Monitoring (Monitor Fabric with RTI and Capacity Events)
Workspace Monitoring Report Templates
Fabric Spark Monitoring (Monitor Spark with RTI)

Accelerators

Samples

Scripts

$${\color{green}NEW!}$$ Mirror CCI Tables for Fabric SQL DB
CI Views
DW/SQL AE Properties
DW Active Requests
DW Copy DMV to Table
DW Queries Running at Timepoint
DW SP Kill Queries

Tools

$${\color{green}NEW!}$$ Fabric Assessment Tool
$${\color{yellow}UPDATED!}$$ Fabric Data Factory Migration Assistant
DAX Performance Tuner MCP Server
Semantic Model MCP Server
Open Mirroring SDK
MicrosoftFabricMgmt PowerShell Module
Gen2 Dedicated Pool to Fabric DW Table Copy
Semantic Model Audit
Copy Warehouse
TPCH Benchmarking
DAX Performance Testing

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Trademarks

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.

SpotX-Official/SpotX

SpotX patcher used for patching the desktop version of Spotify

Patcher for Spotify Desktop Client on Windows

• Requirements • Features • Installation • Uninstall • FAQ • Disclaimer

Requirements

OS: Windows 7-11
Spotify: Official desktop version (Microsoft Store version is not suitable)
PowerShell: 5.1 and above

Features

Blocks all banner, video, and audio ads in the client
Hiding podcasts, episodes, and audiobooks from the homepage (optional)
Block Spotify automatic updates (optional)
Some native experimental features have been changed
Analytics sending has been disabled
Advanced installation parameters

Installation / Update

Choose installation type:

Usual installation (New theme)

During installation, you need to confirm some actions, also contains:

New theme activated (new right and left sidebar, some cover change)
All experimental features included

Just download and run Install_New_theme.bat

Run The following command in PowerShell:

iex "& { $(iwr -useb 'https://raw.githubusercontent.com/SpotX-Official/SpotX/refs/heads/main/run.ps1') } -new_theme"

mirror

iex "& { $(iwr -useb 'https://spotx-official.github.io/SpotX/run.ps1') } -m -new_theme"

Usual installation (Old theme)

During installation, you need to confirm some actions, also contains:

Forced installation of version 1.2.13 (since the old theme was removed in subsequent versions)
Old theme activated
Automatic blocking of Spotify updates
All experimental features included

Just download and run Install_Old_theme.bat

Run The following command in PowerShell:

iex "& { $(iwr -useb 'https://raw.githubusercontent.com/SpotX-Official/SpotX/refs/heads/main/run.ps1') } -v 1.2.13.661.ga588f749 -confirm_spoti_recomended_over -block_update_on"

mirror

iex "& { $(iwr -useb 'https://spotx-official.github.io/SpotX/run.ps1') } -m -v 1.2.13.661.ga588f749 -confirm_spoti_recomended_over -block_update_on"

Full installation

Full installation without confirmation, what does it do?

New theme activated (new right and left sidebar, some cover change)
Hiding podcasts/episodes/audiobooks from the homepage
Activated static theme spotify for lyrics
Hiding ad-like sections
All experimental features included
Removal of Spotify MS if it was found
Installation of the recommended version of Spotify (if another client has already been found, it will be installed over)
Blocking of Spotify updates
After the installation is completed, the client will autorun.

Just download and run Install_Auto.bat

Run The following command in PowerShell:

iex "& { $(iwr -useb 'https://raw.githubusercontent.com/SpotX-Official/SpotX/refs/heads/main/run.ps1') } -confirm_uninstall_ms_spoti -confirm_spoti_recomended_over -podcasts_off -block_update_on -start_spoti -new_theme -adsections_off -lyrics_stat spotify"

mirror

iex "& { $(iwr -useb 'https://spotx-official.github.io/SpotX/run.ps1') } -m -confirm_uninstall_ms_spoti -confirm_spoti_recomended_over -podcasts_off -block_update_on -start_spoti -new_theme -adsections_off -lyrics_stat spotify"

Other types of installations

Installation for premium

Usual installation only without ad blocking, for those who have a premium account, also contains:

New theme activated (new right and left sidebar, some cover change)
Disabled only audio ads in podcasts
All experimental features included

Just download and run Install_Prem.bat

Run The following command in PowerShell:

iex "& { $(iwr -useb 'https://raw.githubusercontent.com/SpotX-Official/SpotX/refs/heads/main/run.ps1') } -premium -new_theme"

mirror

iex "& { $(iwr -useb 'https://spotx-official.github.io/SpotX/run.ps1') } -m -premium -new_theme"

Installing with parameters

You can specify various parameters for a more flexible installation, more details here

Uninstall

Just run Uninstall.bat

Reinstall Spotify (Full uninstall Spotify recommended)

FAQ

Read FAQ

Disclaimer

SpotX is a tool that modifies the official Spotify client, provided as an evaluation version — use it at your own risk.

microsoft/Agents

The Microsoft 365 Agent SDK simplifies building full stack, multichannel, trusted agents for platforms including M365, Teams, Copilot Studio, and Webchat.

Microsoft 365 Agents SDK

With the Microsoft 365 Agents SDK, you can create agents deployable to channels of your choice, such as Microsoft 365 Copilot, Microsoft Teams, Web & Custom Apps and more, with scaffolding to handle the required communication. Developers can use the AI Services of their choice, and make the agents they build available using the channel management capabilities of the SDK.

Developers need the flexibility to integrate agents from any provider or technology stack into their enterprise systems. The Agents SDK simplifies the implementation of agentic patterns using the AI of their choice, allowing them to select one or more services, models, or agents to meet their specific requirements.

Use the Agents SDK to:

Quickly build an agent 'container' with state, storage, and the ability to manage activities and events. Deploy this container across any channel, such as Microsoft 365 Copilot or Microsoft Teams.
Implement agentic patterns without being restricted to a specific technology stack. The Agents SDK is agnostic regarding the AI you choose.
Customize your agent to align with the specific behaviors of clients, such as Microsoft Teams.

Get Started

You can get started right here by scolling up and clicking the 'samples' folder in this repo, selecting your language and reviewing the samples list before picking which one you want to start with (QuickStart is recommended for fundamentals).

Microsoft 365 Copilot is one of many channels supported by this SDK, and a Microsoft 365 Copilot subscription is not required to get started with or use this SDK unless your working specifically with that channel (or others, that require a subscription/service to use their client).

C#, JavaScript & Python Repository links

The source for the client libraries exists for the most part in repositories for each language. This repository is meant to be a jumping off point into those language specific repositories. Issues related to a specific language should be opened in the corresponding repository but cross cutting issues can be opened in this repository.

Language	Repo
General (This repo)	Agents Repository
C# /.NET	Agents-for-net Repository
JavaScript	Agents-for-js Repository
Python	Agents-for-python Repository

Documentation

To learn more about the Agents SDK, you can read our official docs here: Agents SDK Documentation

Related SDKs and Agent Platforms

Semantic Kernel. Semantic Kernel is an SDK that integrates Large Language Models (LLMs) like OpenAI, Azure OpenAI, and Hugging Face with conventional programming languages like C#, Python, and Java. Semantic Kernel achieves this by allowing you to define plugins that can be chained together in just a few lines of code.
Azure AI Foundry. Provides the core backend agent functionality, providing reasoning, retrieval augmentation, observability, among other core functions. Developers can leverage the Azure AI Agent Service or build their agent functionality with individual components from this SDK.
Copilot Studio. Copilot Studio is an agent building platform that can be used with the Microsoft 365 Agents SDK to integrate your agent into your applications & create multi-agent patterns with Copilot Studio Agents. To get started, go to the samples folder in this repo and select the Copilot Studio Client sample in your chosen language.

The Microsoft 365 Agents SDK brings together core components to allow for developers to create, manage and utilize AI Services and third-party SDKs to power orchestration and develop custom agent logic functionality.

Using other services with the Agents SDK

Your use of other services in connection with the Microsoft 365 Agents SDK is governed by the respective agreements for those services, which may include codes of conduct and other restrictions

Contributing

Note for Microsoft intenral developers:

Internal Micrsoft Developers should join the Core identity group Agents SDK Contrib

Non-Microsoft internal developers:

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Recommended VS Code Extensions

To ensure a consistent development environment, we recommend using the following VS Code extensions:

Extension	Description
ESLint	Integrates ESLint into VS Code. Allows you to find an fix problems in JavaScript code.
GitHub Copilot Chat	GitHub Copilot is an AI peer programming tool that helps you write code faster and smarter.
GitHub Codespaces	GitHub Codespaces provides cloud-hosted development environments for any activity - whether it's a long-term project, or a short-term task like reviewing a pull request.
C# Dev Kit	C# Dev Kit helps you manage your code with a solution explorer and test your code with integrated unit test discovery and execution, elevating your C# development experience wherever you like to develop (Windows, macOS, Linux, and even in a Codespace).
Adaptive Card Previewer	The Microsoft Adaptive Card Previewer uses the latest rendering stack for Microsoft Teams to provide a more accurate preview of Adaptive Cards. You can open a side-by-side preview to view changes live, toggle between light, dark, and high-contrast themes.

These are listed in .vscode/extensions.json, so VS Code should prompt you to install them when you open the project.

Trademarks

KelvinTegelaar/CIPP-API

No description/README provided.

dotnet/core

.NET news, announcements, release notes, and more!

.NET Release Notes

Welcome to the home of .NET release notes and news.

Releases

Releases under active support or development:

Version	Release Date	Release type	Support phase	Latest Patch Version	End of Support
.NET 11.0	November 10, 2026	STS	Preview	11.0.0-preview.3	TBD
.NET 10.0	November 11, 2025	LTS	Active	10.0.6	November 14, 2028
.NET 9.0	November 12, 2024	STS	Active	9.0.15	November 10, 2026
.NET 8.0	November 14, 2023	LTS	Active	8.0.26	November 10, 2026

Discussions

Follow GitHub Discussions, where you will find the latest news on releases, including PSAs and CVEs.

You can subscribe to discussions with the following RSS feeds:

Category	GitHub Discussions	RSS Feed
All Discussions	🔗	🔗
News	🔗	🔗
General	🔗	🔗

Azure/PSRule.Rules.Azure

Rules to validate Azure resources and infrastructure as code (IaC) using PSRule.

PSRule for Azure

A suite of rules to test Azure resources and Infrastructure as Code (IaC) using PSRule. The built-in rules test the configuration of Azure resources for security, reliability, and much more. Rules can be created to enforce your own policies and standards.

Features of PSRule for Azure include:

Learn by example - Fix issues quickly, and learn how to improve your Infrastructure as Code..
Framework aligned - Apply principals of Azure Well-Architected Framework to your workloads.
Start day one - Leverage over 500 pre-built rules to test Azure resources.
DevOps integrated - Test Azure infrastructure as code such as Bicep or Azure Resource Manager templates.
Cross-platform - Run locally or in the cloud on MacOS, Linux, and Windows.
Open community - Open source rules for the Azure community.

Project objectives

Ready to go:
- Provide a Azure Well-Architected Framework aligned suite of rules for validating Azure resources.
- Provide meaningful information to allow remediation.
DevOps:
- Resources and Azure code can be tested before deployment within DevOps workflows.
- Allow pull request (PR) validation to prevent invalid configuration from being merged.
Enterprise ready:
- Rules can be directly adopted and additional enterprise specific rules can be layered on.
- Provide regular baselines to allow progressive adoption.

Support

This project uses GitHub Issues to track bugs and feature requests. Before logging an issue please see our troubleshooting guide.

Please search the existing issues before filing new issues to avoid duplicates.

For new issues, file your bug or feature request as a new issue.
For help, discussion, and support questions about using this project, join or start a discussion.

If you have any problems with the PSRule engine, please check the project GitHub issues page instead.

Support for this project/ product is limited to the resources listed above.

Getting the modules

This project requires the PSRule and Az PowerShell modules. For details on each see install.

You can download and install these modules from the PowerShell Gallery.

Module	Description	Downloads / instructions
PSRule.Rules.Azure	Validate Azure resources and infrastructure as code using PSRule.	latest / instructions

For rule and integration modules see related projects.

Getting started

PSRule for Azure provides two methods for analyzing Azure resources:

Pre-flight - Before resources are deployed from Azure Resource Manager templates.
In-flight - After resources are deployed to an Azure subscription.

For specific use cases see scenarios. For additional details see the FAQ.

To get started with a sample repository, see PSRule for Azure Quick Start on GitHub.

Using with GitHub Actions

The following example shows how to setup GitHub Actions to validate templates pre-flight.

See Creating a workflow file.
Reference microsoft/ps-rule with modules: 'PSRule.Rules.Azure'.

For example:

# Example: .github/workflows/analyze-arm.yaml

#
# STEP 1: Template validation
#
name: Analyze templates
on:
  push:
    branches:
    - main
  pull_request:
    branches:
    - main
jobs:
  analyze_arm:
    name: Analyze templates
    runs-on: ubuntu-latest
    steps:

    - name: Checkout
      uses: actions/checkout@v3

    # STEP 2: Run analysis against exported data
    - name: Analyze Azure template files
      uses: microsoft/ps-rule@v2.9.0
      with:
        modules: 'PSRule.Rules.Azure'  # Analyze objects using the rules within the PSRule.Rules.Azure PowerShell module.

Using with Azure Pipelines

The following example shows how to setup Azure Pipelines to validate templates pre-flight.

Install PSRule extension for Azure DevOps marketplace.
Create a new YAML pipeline with the Starter pipeline template.
Add the Install PSRule module task.
- Set module to PSRule.Rules.Azure.
Add the PSRule analysis task.
- Set input type to repository.
- Set modules to PSRule.Rules.Azure.

For example:

# Example: .azure-pipelines/analyze-arm.yaml

#
# STEP 2: Template validation
#
jobs:
- job: 'analyze_arm'
  displayName: 'Analyze templates'
  pool:
    vmImage: 'ubuntu-22.04'
  steps:

  # STEP 3: Install PSRule.Rules.Azure from the PowerShell Gallery
  - task: ps-rule-install@2
    displayName: Install PSRule.Rules.Azure
    inputs:
      module: 'PSRule.Rules.Azure'   # Install PSRule.Rules.Azure from the PowerShell Gallery.

  # STEP 4: Run analysis against exported data
  - task: ps-rule-assert@2
    displayName: Analyze Azure template files
    inputs:
      modules: 'PSRule.Rules.Azure'   # Analyze objects using the rules within the PSRule.Rules.Azure PowerShell module.

Using locally

The following example shows how to setup PSRule locally to validate templates pre-flight.

Install the PSRule.Rules.Azure module and dependencies from the PowerShell Gallery.
Run analysis against repository files.

For example:

# STEP 1: Install PSRule.Rules.Azure from the PowerShell Gallery
Install-Module -Name 'PSRule.Rules.Azure' -Scope CurrentUser;

# STEP 2: Run analysis against exported data
Assert-PSRule -Module 'PSRule.Rules.Azure' -InputPath 'out/templates/' -Format File;

Export in-flight resource data

The following example shows how to setup PSRule locally to validate resources running in a subscription.

Install the PSRule.Rules.Azure module and dependencies from the PowerShell Gallery.
Connect and set context to an Azure subscription from PowerShell.
Export the resource data with the Export-AzRuleData cmdlet.
Run analysis against exported data.

For example:

# STEP 1: Install PSRule.Rules.Azure from the PowerShell Gallery
Install-Module -Name 'PSRule.Rules.Azure' -Scope CurrentUser;

# STEP 2: Authenticate to Azure, only required if not currently connected
Connect-AzAccount;

# Confirm the current subscription context
Get-AzContext;

# STEP 3: Exports a resource graph stored as JSON for analysis
Export-AzRuleData -OutputPath 'out/templates/';

# STEP 4: Run analysis against exported data
Assert-PSRule -Module 'PSRule.Rules.Azure' -InputPath 'out/templates/';

Additional options

By default, resource data for the current subscription context will be exported.

To export resource data for specific subscriptions use:

-Subscription - to specify subscriptions by id or name.
-Tenant - to specify subscriptions within an Azure Active Directory Tenant by id.

For example:

# Export data from two specific subscriptions
Export-AzRuleData -Subscription 'Contoso Production', 'Contoso Non-production';

To export specific resource data use:

-ResourceGroupName - to filter resources by Resource Group.
-Tag - to filter resources based on tag.

For example:

# Export information from two resource groups within the current subscription context
Export-AzRuleData -ResourceGroupName 'rg-app1-web', 'rg-app1-db';

To export resource data for all subscription contexts use:

-All - to export resource data for all subscription contexts.

For example:

# Export data from all subscription contexts
Export-AzRuleData -All;

To filter results to only failed rules, use Invoke-PSRule -Outcome Fail. Passed, failed and error results are shown by default.

For example:

# Only show failed results
Invoke-PSRule -InputPath 'out/templates/' -Module 'PSRule.Rules.Azure' -Outcome Fail;

The output of this example is:

   TargetName: storage

RuleName                            Outcome    Recommendation
--------                            -------    --------------
Azure.Storage.UseReplication        Fail       Storage accounts not using GRS may be at risk
Azure.Storage.SecureTransferRequ... Fail       Storage accounts should only accept secure traffic
Azure.Storage.SoftDelete            Fail       Enable soft delete on Storage Accounts

A summary of results can be displayed by using Invoke-PSRule -As Summary.

For example:

# Display as summary results
Invoke-PSRule -InputPath 'out/templates/' -Module 'PSRule.Rules.Azure' -As Summary;

The output of this example is:

RuleName                            Pass  Fail  Outcome
--------                            ----  ----  -------
Azure.ACR.MinSku                    0     1     Fail
Azure.AppService.PlanInstanceCount  0     1     Fail
Azure.AppService.UseHTTPS           0     2     Fail
Azure.Resource.UseTags              73    36    Fail
Azure.SQL.ThreatDetection           0     1     Fail
Azure.SQL.Auditing                  0     1     Fail
Azure.Storage.UseReplication        1     7     Fail
Azure.Storage.SecureTransferRequ... 2     6     Fail
Azure.Storage.SoftDelete            0     8     Fail

Scenarios

For walk through examples of PSRule for Azure module usage see:

Rule reference

PSRule for Azure includes rules across five pillars of the Microsoft Azure Well-Architected Framework.

Rules for architecture excellence

To view a list of rules by Azure resources see:

Rules by resource

Baseline reference

For a list of baselines you can use in your configuration see Baselines.

Language reference

PSRule for Azure extends PowerShell with the following cmdlets.

Commands

PSRule for Azure included the following cmdlets:

Export-AzRuleData - Export resource configuration data from Azure subscriptions.
Export-AzRuleTemplateData - Export resource configuration data from Azure templates.
Export-AzPolicyAssignmentData - Export policy assignment data.
Export-AzPolicyAssignmentRuleData - Export JSON based rules from policy assignment data.
Get-AzRuleTemplateLink - Get a metadata link to a Azure template file.
Get-AzPolicyAssignmentDataSource - Get policy assignment sources.

Concepts

To find out more, look at these conceptual topics:

Getting started:
- How to install PSRule for Azure
- Creating your pipeline
Testing infrastructure as code:
Setup:

Related projects

For a list of projects and integrations see Related projects.

Changes and versioning

This repository uses semantic versioning to declare breaking changes. For details please see the changes and versioning.

Contributing

This project welcomes contributions and suggestions. If you are ready to contribute, please visit the contribution guide.

Code of Conduct

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Maintainers

Bernie White

License

This project is licensed under the MIT License.

Trademarks

microsoft/skills-for-fabric

A collection of skills and MCP systems to enable users of CLI, VSCode, Claude to operate over Microsoft Fabric

Skills for Fabric

Agent Skills for Microsoft Fabric

AI agent skills for Microsoft Fabric developers, data engineers, admins, and consumers.

Optimized for GitHub Copilot CLI, with cross‑tool compatibility for VS Code Copilot, Claude Code, Cursor, Codex/Jules, and Windsurf.

📘 Documentation • 🔐 Security • 🤝 Contributing • 🐞 Report a Bug

Why Skills for Fabric?

Skills for Fabric bridges the gap between AI coding assistants and Microsoft Fabric's enterprise data platform. We provide first-party, production-ready agent skills that enable AI tools to safely author, query, and operate complex Fabric workloads—from Spark pipelines to semantic models—while maintaining enterprise security and governance standards.

✨ What are Skills for Fabric?

Skills for Fabric (also referred to as Agent Skills) provide a standardized, secure, and extensible way for AI coding agents to author, query, operate, and govern Microsoft Fabric workloads.

These skills allow AI tools to act as Fabric‑aware agents—capable of understanding workspaces, Lakehouses, Warehouses, Eventhouses, semantic models, and capacity settings—while respecting Microsoft security, governance, and Responsible AI requirements.

The project follows the same design principles used across other Microsoft‑hosted skill repositories:

✅ Explicit authentication and authorization
✅ Clear separation of instructions vs user content
✅ No arbitrary code execution
✅ Enterprise‑grade security and compliance
✅ Tool‑agnostic agent compatibility

🆚 Skills vs Prompt‑Only Approaches

Unlike prompt‑only workflows, Skills for Fabric:

Use authenticated Microsoft Fabric APIs
Enforce safe, validated operations
Understand Fabric resource types and boundaries
Prevent prompt injection and unsafe execution
Produce deterministic, auditable actions

This makes agent interactions reliable, repeatable, and enterprise‑ready.

🧱 Skills vs Agents

Concept	Description
Skill	A single, focused capability (for example: run Spark, query SQL, manage KQL)
Agent	An orchestrator that combines multiple skills to achieve a goal

Agents are built on top of skills.

🧠 Supported Personas & Scenarios

Skills are organized by persona and intent, enabling both focused and end‑to‑end workflows.

👩‍💻 Developers & Data Engineers (Authoring)

Create and manage Fabric resources
Build Spark ETL / ELT pipelines
Author SQL objects and KQL assets
Automate deployments and CI/CD flows

📊 Consumers & Analysts (Consumption)

Query Lakehouse tables interactively
Run SQL, DAX, and KQL without drivers
Explore metadata and monitor usage

🛡️ Admins & Platform Owners

Capacity planning and optimization
Governance and security validation
Cost, performance, and usage analysis

🤖 Cross‑Workload Agents

Medallion architectures (Bronze → Silver → Gold)
Migration and modernization
Data quality checks and observability

🚀 Example Use Cases

Scenario	What the Agent Does
Analytics PDF Report	Analyzes Fabric data and generates a production‑ready PDF report
Document My Workspace	Inspects Fabric workspaces and produces structured documentation
NYC Taxi Medallion Project	Ingests public data, builds Spark pipelines, and exposes SQL views
Dashboard App	Creates an interactive dashboard connected to Fabric data

📦 Installation

GitHub Copilot CLI (Recommended)

Always start by connecting to the Skills for Fabric marketplace

/plugin marketplace add microsoft/skills-for-fabric

Install all skills

/plugin install skills-for-fabric@fabric-collection

Install by persona

# Authoring (developers, automation, CI/CD)
/plugin install fabric-authoring@fabric-collection

# Consumption (interactive analytics)
/plugin install fabric-consumption@fabric-collection

Filter by engine or endpoint

/plugin install skills-for-fabric@fabric-collection --filter "spark-*"
/plugin install skills-for-fabric@fabric-collection --filter "sqldw-*"
/plugin install skills-for-fabric@fabric-collection --filter "eventhouse-*"

Manual Installation

git clone https://github.com/microsoft/skills-for-fabric.git
cd skills-for-fabric

# Windows
.\\install.ps1

# macOS / Linux
./install.sh

🔐 Authentication

All Fabric operations require Azure AD authentication:

az login
az account get-access-token --resource https://api.fabric.microsoft.com

No secrets or tokens are stored by the skills.

🧩 Skill Catalog

✍️ Authoring Skills

Skill	Purpose
sqldw-authoring-cli	Author Warehouses, Lakehouse SQL Endpoints, Mirrored Databases
spark-authoring-cli	Build Fabric Spark and Data Engineering workflows
eventhouse-authoring-cli	Manage KQL tables, ingestion, policies, and functions
powerbi-authoring-cli	Create and deploy Power BI semantic models

📈 Consumption Skills

Skill	Description
sqldw-consumption-cli	Query Warehouses and SQL Endpoints
spark-consumption-cli	Analyze Lakehouse tables interactively
eventhouse-consumption-cli	Run read‑only KQL queries
powerbi-consumption-cli	Query semantic models and execute DAX

🧰 Utility Skills

Skill	Description
check-updates	Automatically checks for marketplace updates

/skills-for-fabric:check-updates

🤖 Agents

Agents orchestrate multiple skills across workloads.

Agent	Purpose
FabricDataEngineer	Medallion architectures, ETL/ELT, migration, data quality
FabricAdmin	Capacity, governance, security, cost, observability

Agent definitions live in agents/.

🔄 Automatic Updates

At the start of each session, the first invoked skill:

Checks GitHub releases
Compares against the installed version
Displays changelog and update instructions

This check runs once per session and is non‑blocking.

🧩 Cross‑Tool Compatibility

Tool	Setup
GitHub Copilot CLI	Automatic via plugin system
VS Code Copilot	`.github/skills/`
Claude Code	`compatibility/CLAUDE.md`
Cursor	`compatibility/.cursorrules`
Codex / Jules	`compatibility/AGENTS.md`
Windsurf	`compatibility/.windsurfrules`

Install scripts configure this automatically.

🔗 MCP Server Registration

# Windows
.\\mcp-setup\\register-fabric-mcp.ps1

# macOS / Linux
./mcp-setup/register-fabric-mcp.sh

See mcp-setup/README.md for details.

🔒 Security & Responsible AI

Security

✅ Secret scanning (TruffleHog, Gitleaks)
✅ Prompt‑injection protection
✅ No arbitrary code execution

Report vulnerabilities via SECURITY.md.

Responsible AI

Clear instruction / data separation
Input validation and sanitization
Secret redaction in outputs
Tested against OWASP LLM Top 10

📊 Data Handling & Privacy

Data processed locally or via authenticated Fabric APIs
No data sent to third‑party services
Azure AD + GitHub Secrets for credentials
Audit logging for executions

🐞 Reporting Issues

Please file structured issues via GitHub Issues.

Do not include secrets or tokens.

🤝 Contributing

We welcome community contributions.

All pull requests must:

✅ Pass tests
✅ Pass security scans
✅ Have CODEOWNER approval
✅ Contain no secrets

📚 Repository Structure

skills-for-fabric/
├── agents/
├── skills/
├── compatibility/
├── docs/
│   ├── compliance/
│   └── assets/
├── mcp-setup/
├── install.ps1
├── install.sh
└── README.md

📜 License

This project is licensed under the MIT License.

Built with ❤️ for the Microsoft Fabric community

microsoftgraph/microsoft-graph-docs-contrib

Documentation for the Microsoft Graph REST API

Microsoft Graph documentation

Thank you for your interest in Microsoft Graph documentation! For the best experience, we recommend you view this content on Microsoft Learn.

Give us your feedback

Your feedback is important to us.

To let us know about any questions or issues you find in the documentation, leave feedback using the standard experience.
We also encourage you to fork, make the fix, and do a pull request of your proposed changes. See CONTRIBUTING.md for contributing guidelines.
To let us know about your programming experience, what you would like to see in future versions, code samples, and so on, enter your suggestions and ideas at Microsoft 365 Developer Platform Tech Community.

Code of conduct

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

mandiant/flare-vm

A collection of software installations scripts for Windows systems that allows you to easily setup and maintain a reverse engineering environment on a VM.

FLARE-VM

Welcome to FLARE-VM - a collection of software installations scripts for Windows systems that allows you to easily setup and maintain a reverse engineering environment on a virtual machine (VM). FLARE-VM was designed to solve the problem of reverse engineering tool curation and relies on two main technologies: Chocolatey and Boxstarter. Chocolatey is a Windows-based Nuget package management system, where a "package" is essentially a ZIP file containing PowerShell installation scripts that download and configure a specific tool. Boxstarter leverages Chocolatey packages to automate the installation of software and create repeatable, scripted Windows environments.

Requirements

FLARE-VM should ONLY be installed on a virtual machine. The VM should satisfy the following requirements:

Windows ≥ 10
PowerShell ≥ 5
Disk capacity of at least 60 GB and memory of at least 2GB
Usernames without spaces or other special characters
Internet connection
Tamper Protection and any Anti-Malware solution (e.g., Windows Defender) disabled, preferably via Group Policy
Windows Updates Disabled

Installation instruction

This section documents the steps to install FLARE-VM. You may also find useful the Building a VM for Reverse Engineering and Malware Analysis! Installing the FLARE-VM video.

Pre-installation

Prepare a Windows 10+ virtual machine
- Install Windows in the virtual machine, for example using the raw Windows 10 ISO from https://www.microsoft.com/en-us/software-download/windows10ISO
- Ensure the requirements above are satisfied, including:
  - Disable Windows Updates (at least until installation is finished)
    - https://www.windowscentral.com/how-stop-updates-installing-automatically-windows-10
  - Disable Tamper Protection and any Anti-Malware solution (e.g., Windows Defender), preferably via Group Policy.
    - GPO: https://stackoverflow.com/questions/62174426/how-to-permanently-disable-windows-defender-real-time-protection-with-gpo
    - Non-GPO - Manual: https://www.maketecheasier.com/permanently-disable-windows-defender-windows-10/
    - Non-GPO - Automated: https://github.com/ionuttbara/windows-defender-remover
    - Non-GPO - Semi-Automated (User needs to toggle off Tamper Protection): https://github.com/AveYo/LeanAndMean/blob/main/ToggleDefender.ps1
Take a VM snapshot so you can always revert to a state before the FLARE-VM installation
NOTE for IDA Pro: If you are installing IDA Pro via idapro.vm, you must place your IDA Pro installer (and optionally, your license file) on the Desktop before running the FLARE-VM installer.

FLARE-VM installation

Open a PowerShell prompt as administrator
Download the installation script installer.ps1 to your Desktop:
- (New-Object net.webclient).DownloadFile('https://raw.githubusercontent.com/mandiant/flare-vm/main/install.ps1',"$([Environment]::GetFolderPath("Desktop"))\install.ps1")
Unblock the installation script:
- Unblock-File .\install.ps1
Enable script execution:
- Set-ExecutionPolicy Unrestricted -Force
  - If you receive an error saying the execution policy is overridden by a policy defined at a more specific scope, you may need to pass a scope in via Set-ExecutionPolicy Unrestricted -Scope CurrentUser -Force. To view execution policies for all scopes, execute Get-ExecutionPolicy -List
Finally, execute the installer script as follow:
- .\install.ps1
  - To pass your password as an argument: .\install.ps1 -password <password>
  - To use the CLI-only mode with minimal user interaction: .\install.ps1 -password <password> -noWait -noGui
  - To use the CLI-only mode with minimal user interaction and a custom config file: .\install.ps1 -customConfig <config.xml> -password <password> -noWait -noGui
After installation it is recommended to switch to host-only networking mode and take a VM snapshot

Installer Parameters

Below are the CLI parameter descriptions.

PARAMETERS
    -password <String>
        Current user password to allow reboot resiliency via Boxstarter. The script prompts for the password if not provided.

    -noPassword [<SwitchParameter>]
        Switch parameter indicating a password is not needed for reboots.

    -customConfig <String>
        Path to a configuration XML file. May be a file path or URL.

    -customLayout <String>
        Path to a taskbar layout XML file. May be a file path or URL.

    -noWait [<SwitchParameter>]
        Switch parameter to skip installation message before installation begins.

    -noGui [<SwitchParameter>]
        Switch parameter to skip customization GUI.

    -noReboots [<SwitchParameter>]
        Switch parameter to prevent reboots (not recommended).

    -noChecks [<SwitchParameter>]
        Switch parameter to skip validation checks (not recommended).

Get full usage information by running Get-Help .\install.ps1 -Detailed.

Installer GUI

The Installer GUI is display after executing the validation checks and installing Boxstarter and Chocolatey (if they are not installed already). Using the installer GUI you may customize:

Package selection from FLARE-VM and Chocolatey community
Environment variable paths

Configuration

The installer will download config.xml from the FLARE-VM repository. This file contains the default configuration, including the list of packages to install and the environment variable paths. You may use your own configuration by specifying the CLI-argument -customConfig and providing either a local file path or URL to your config.xml file. For example:

.\install.ps1 -customConfig "https://raw.githubusercontent.com/mandiant/flare-vm/main/config.xml"

Taskbar Layout

The installer will use CustomStartLayout.xml from the FLARE-VM repository. This file contains the default taskbar layout. You may use your own configuration by specifying the CLI-argument -customLayout and providing a local file path or URL to your CustomStartLayout.xml file. For example:

.\install.ps1 -customLayout "https://raw.githubusercontent.com/mandiant/flare-vm/main/CustomStartLayout.xml"

Things to Consider:

Items in the .xml that are not installed will not display in the taskbar (no broken links will be pinned)
Only applications (.exe files) or shortcuts to applications can be pinned.
If you would like to pin something that isn't an application, consider creating a shortcut that points to cmd.exe or powershell with arguments supplied that will perform that actions you would like.
If you would like to make something run with admin rights, consider making a shortcut using VM-Install-Shortcut with the flag -runAsAdmin and pinning the shortcut.

Post installation steps

You can include any post installation step you like in the configuration inside the tags apps, services, path-items, registry-items, and custom-items.

For example:

To show known file extensions:

    <registry-items>
        <registry-item name="Show known file extensions" path="HKCU:\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced" value="HideFileExt" type="DWord" data="0"/>
    </registry-items>

For more examples, check the default configuration file: config.xml.

Contributing

Check our CONTRIBUTING guide to learn how to contribute to the project.

Troubleshooting

If your installation fails, please attempt to identify the reason for the installation error by reading through the log files listed below on your system:

%VM_COMMON_DIR%\log.txt
%PROGRAMDATA%\chocolatey\logs\chocolatey.log
%LOCALAPPDATA%\Boxstarter\boxstarter.log

Ensure you are running the latest version of the FLARE-VM installer and that your VM satisfies the requirements.

Installer Error

If the installation failed due to an issue in the installation script (e.g., install.ps1), report the bug in FLARE-VM. Provide all the information requested to ensure we are able to help you.

Note: Rarely should install.ps1 be the reason for an installation failure. Most likely it is a specific package or set of packages that are failing (see below).

Package Error

Packages fail to install from time to time -- this is normal. The most common reasons are outlined below:

Failure or timeout from Chocolatey or MyGet to download a .nupkg file
Failure or timeout due to remote host when downloading a tool
Intrusion Detection System (IDS) or AV product (e.g., Windows Defender) prevents a tool download or removes the tool from the system
Host specific issue, for example when using an untested version
Tool fails to build due to dependencies
Old tool URL (e.g., HTTP STATUS 404)
Tool's SHA256 hash has changed from what is hardcoded in the package installation script

Reasons 1-4 are difficult for us to fix since we do not control them. If an issue related to reasons 1-4 is filed, it is unlikely we will be able to assist.

We can help with reasons 5-7 and welcome the community to contribute fixes as well! Please report the bug in VM-Packages providing all the information requested.

Updates

Note that package updates are best effort and that updates are not being tested. If you encounter errors, perform a fresh FLARE-VM install.

Mailing List

Subscribe to the FLARE mailing list for community announcements! Email "subscribe" to flare-external@google.com.

Legal Notice

This download configuration script is provided to assist cyber security analysts in creating handy and versatile toolboxes for malware analysis environments. It provides a convenient interface for them to obtain a useful set of analysis tools directly from their original sources. Installation and use of this script is subject to the Apache 2.0 License. You as a user of this script must review, accept and comply with the license terms of each downloaded/installed package. By proceeding with the installation, you are accepting the license terms of each package, and acknowledging that your use of each package will be subject to its respective license terms.

MicrosoftDocs/microsoftgraph-docs-powershell

Microsoft Open Source Code of Conduct

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Azure/AzureLocal-Supportability

Welcome to the Azure Local Supportability Forum! This is where the Azure Local team will track troubleshooting guides and issues with Azure Local. We will maintain this repo in order to provide a central location for community driven supportability content.

Azure Local Supportability Forum

This is a public repository for all of Azure Local Troubleshooting guides (TSGs), known issues and reporting feedback - this repo is intended to provide a central location for community driven supportability content. This is the material that is referenced by Customer Support Services when a ticket is created, by Azure Local engineering responding to an incident, and by users when self discovering resolutions to active system issues.

Azure Stack HCI is now part of Azure Local. Learn more.

Troubleshooting guides (TSGs) are grouped by categories and stored in relevantly named subdirectories. Each directory contains a README that lists the guides. The following are the categories of guides that are stored in relevantly named directories:

Deployment - Prerequisites, AD, Software Download, OS install, Registration, Arc extensions and Deployment (Portal & ARM templates).
Update - Health Check, Sideloading, Update method (Azure Update Manager & PowerShell).
Upgrade - Upgrade from version 22H2 to 23H2.
Solution Extension - Solution extension.
LCM - Lifecycle Manager.
Infra Lifecycle Operations - Add Server, Repair Server.
Arc VMs - VM lifecycle management, licensing, extensions, networking and storage.
Security - WDAC, BitLocker, Secret Rotation, Syslog, Defender for Cloud.
Networking - Arc Gateway, Outbound Connectivity, TOR Configuration.
Monitoring - Insights, Metric and Alerts.
Azure Virtual Desktop - Azure Virtual Desktop.
Azure Kubernetes - Deployment, Networking, Update.
Storage - Storage.
Environment Validator - Environment Validation during deploy, update, scaleout, upgrade etc.
Arc Registration - Arc Registration.

Bug Reports

IMPORTANT: An inability to meet the below requirements for bug reports are subject to being closed by maintainers and routed to official Azure support channels to provide the proper support experience to resolve user issues.

Bug reports filed on this repository should follow the default issue template that is shown when opening a new issue. Please do not share any personal data. The template contains the following fields:

Bug Description
Repro Steps
Expected Behavior
Environment
- Azure Local build (release version)
- 1-node vs. multi-nodes, etc.
- Production vs. Non-production
- Region
Screenshots (do not share personal data)
Correlation ID (from log collection)

At a bare minimum, issues reported on this repository must:

Be reproducible outside of the current system

This means that if you file an issue that would require direct access to your system and/or Azure resources you will be redirected to open an Azure support ticket. Microsoft employees may not ask for personal / subscription information on Github.
- For example, if your issue is related to custom scenarios such as custom network devices, configuration, authentication issues related to your Azure subscription, etc.

Contain the following information:

A good title: Clear, relevant and descriptive - so that a general idea of the problem can be grasped immediately
Description: Before you go into the detail of steps to replicate the issue, you need a brief description.
- Assume that whomever is reading the report is unfamiliar with the issue/system in question
Clear, concise steps to replicate the issue outside of your specific system.
- These should let anyone clearly see what you did to see the problem, and also allow them to recreate it easily themselves. This section should also include results - both expected and the actual - along with relevant URLs.
Be sure to include any supporting information you might have that could aid the developers.
- This includes YAML files/deployments, scripts to reproduce, exact commands used, screenshots, etc.

Contributing

📝 For Contributing Guidelines, please refer to CONTRIBUTING.md

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Legal Notices

Microsoft and any contributors grant you a license to the Microsoft documentation and other content in this repository under the Creative Commons Attribution 4.0 International Public License, see the LICENSE file, and grant you a license to any code in the repository under the MIT License, see the LICENSE-CODE file.

Microsoft, Windows, Microsoft Azure and/or other Microsoft products and services referenced in the documentation may be either trademarks or registered trademarks of Microsoft in the United States and/or other countries. The licenses for this project do not grant you rights to use any Microsoft names, logos, or trademarks. Microsoft's general trademark guidelines can be found at http://go.microsoft.com/fwlink/?LinkID=254653.

Privacy information can be found at https://privacy.microsoft.com/en-us/

Microsoft and any contributors reserve all others rights, whether under their respective copyrights, patents, or trademarks, whether by implication, estoppel or otherwise.

microsoft/work-iq

MCP Server and CLI for accessing Work IQ

Microsoft Work IQ — Plugin Marketplace

The official Microsoft Work IQ plugin collection for GitHub Copilot ✨

Extend the power of GitHub Copilot with Work IQ plugins — MCP servers, skills, and tools that connect AI assistants to your Microsoft 365 data.

⚠️ Public Preview: Features and APIs may change.

To access Microsoft 365 tenant data, the WorkIQ CLI and MCP Server need to be consented to permissions that require administrative rights on the tenant. On first access, a consent dialog appears. If you are not an administrator, contact your tenant administrator to grant access.

For Tenant Administrators: See the Tenant Administrator Enablement Guide for detailed instructions on granting admin consent, including a quick one-click consent URL.

For more information, see Microsoft's User and Admin Consent Overview.

📋 Prerequisites

Before getting started, ensure you have Node.js (which includes NPM and NPX) installed:

Node.js 18+ — Download from nodejs.org

You can verify your installation by running:

node --version
npm --version

💡 Why Node.js? WorkIQ uses NPX to run the MCP server. NPX is included automatically with NPM, which comes bundled with Node.js.

🚀 Quick Start with GitHub Copilot CLI

# 1. Open GitHub Copilot CLI
copilot

# 2. Add this plugin marketplace (one-time setup)
/plugin marketplace add microsoft/work-iq

# 3. Install any plugin
/plugin install workiq@work-iq
/plugin install microsoft-365-agents-toolkit@work-iq
/plugin install workiq-productivity@work-iq

That's it! Restart Copilot CLI and start using the plugin:

You: What are my upcoming meetings this week?
You: Summarize emails from Sarah about the budget
You: Find documents I worked on yesterday

📦 Alternative: Standalone MCP Installation

If you prefer to run WorkIQ as a standalone MCP server:

# Install globally
npm install -g @microsoft/workiq

# Run the MCP server
workiq mcp

Or use npx without installing:

npx -y @microsoft/workiq mcp

Or add it as an MCP server in your coding agent or IDE:

{
  "workiq": {
    "command": "npx",
    "args": ["-y", "@microsoft/workiq@latest", "mcp"],
    "tools": ["*"]
  }
}

Note: please refer to use MCP servers in VS Code for the configuration instructions relative to Visual Studio Code.

Updating

If you installed WorkIQ globally with npm, run the following command to update to the latest version:

npm update -g @microsoft/workiq

To verify the installed version after updating:

workiq version

💡 Using npx? If you run WorkIQ via npx -y @microsoft/workiq mcp, npx automatically fetches the latest version each time, so no manual update step is needed.

🎯 What You Can Query

Data Type	Example Questions
Emails	"What did John say about the proposal?"
Meetings	"What's on my calendar tomorrow?"
Documents	"Find my recent PowerPoint presentations"
Teams	"Summarize today's messages in the Engineering channel"
People	"Who is working on Project Alpha?"

📖 CLI Reference

Commands

Command	Description
`workiq accept-eula`	Accept the End User License Agreement (EULA)
`workiq ask`	Ask a question to a specific agent or run in interactive mode
`workiq mcp`	Start MCP stdio server for agent communication
`workiq version`	Show version information

Global Options

Option	Description	Default
`-t, --tenant-id <tenant-id>`	The Entra tenant ID to use for authentication	`common`
`--version`	Show version information
`-?, -h, --help`	Show help and usage information

`workiq ask` Options

Option	Description
`-q, --question <question>`	The question to ask the agent

Examples

# Accept the EULA (required on first use)
workiq accept-eula

# Interactive mode
workiq ask

# Ask a specific question
workiq ask -q "What meetings do I have tomorrow?"

# Use a specific tenant
workiq ask -t "your-tenant-id" -q "Show my emails"

# Start MCP server
workiq mcp

🔌 Available Plugins

Plugin	Description
workiq	Query Microsoft 365 data with natural language — emails, meetings, documents, Teams messages, and more.
microsoft-365-agents-toolkit	Toolkit for building M365 Copilot declarative agents — scaffolding, manifest authoring, and capability configuration.
workiq-productivity	Read-only WorkIQ productivity insights — email triage, meeting costs, org charts, channel audits, and more.

📖 See PLUGINS.md for the full plugin catalog with detailed skill listings, example prompts, MCP server info, and installation instructions.

Platform Support

The WorkIQ CLI and MCP Server are supported on win_x64, win_arm64, linux_x64, linux_arm64, osx_x64 and osx_arm64.

🤝 Contributing

We welcome new plugins! See CONTRIBUTING.md for the full guide. In short:

Create your plugin under plugins/{your-plugin}/
Add .mcp.json, README.md, and skills/{name}/SKILL.md
Register it in .github/plugin/marketplace.json
Submit a pull request

📄 License

By using this package, you accept the license agreement. See NOTICES.TXT and EULA within the package for legal terms.

Trademarks

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft’s Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos is subject to those third-party's policies.