KO
|
EN
gitlite โ search
Search
#python
#java
#python3
#arduino
#golang
#machine-learning
#rust
#html
#flask
#javascript
#seismology
#nodejs
mpf
โ 65
Open GitHub โ
Azure Minimum Permissions Finder
Download README (.md)
Explore Similar Repositories
mpflow
:
No description available.
mpfshell-lite
:
๐พ The lightweight version of the mpfshell is for pure CUI drivers.
mpfhandler
:
a mutiple processes timed rotate logging file handler(base logging.RotatingFileHandler, ConcurrentLogHandler)
MPFmaster
:
EA Pathfinder Music Tool
mpf-monitor
:
Graphical utilty which connects to MPF to let you visually control, troubleshoot, and see the status of the machine
// repository documentation
Was this content helpful?
โ 0
(0 ratings)
Select Rating:
โ
โ
โ
โ
โ
Submit Feedback
Recent Feedback
×
Download README
Do you want to download the
README.md
file for
mpf
?
Download (.md)
# MPF utility (Azure Deployment Minimum Permissions Finder) [](https://scorecard.dev/viewer/?uri=github.com/Azure/mpf) This utility finds the minimum permissions required for a given Azure deployment. This can help when you need to figure out the details of what permissions a service principal or managed identity will need to deploy a given ARM template, Bicep file, or Terraform module. Similarly, when assigning a Service Principal / Managed Identity to an Azure Policy Assignment, this utility can help you figure out the minimum permissions required by the Service Principal / Managed Identity to enforce/remediate the policy. It is recommended that the utility is used in a **development** or **test environment** to find the minimum permissions required. ## How It Works  The overview of how this utility works is as follows: - The key parameters the utility needs are the **Service Principal details** (Client ID, Secret, and Object ID) and details needed for the specific deployment provider: - ARM: ARM template file and parameters file needed - Bicep: Bicep file, parameters file, and the Bicep executable path needed - Terraform: Terraform module directory and variables file needed - The utility **removes any existing Role Assignments for the provided Service Principal** - A Custom Role is created (seeded with a small bootstrap set of permissions required to run the deployment loop, then incrementally updated based on authorization errors) - The Service Principal (SP) is assigned the new custom role - For the above steps, the utility uses **management-plane credentials** from `DefaultAzureCredential` (commonly backed by an `az login` session in local development) to create/delete custom roles, manage role assignments, and create/delete resource groups. - The deployment itself is executed using the provided **Service Principal credentials**, and authorization errors returned by Azure (ARM/Bicep) or Terraform are parsed to discover missing permissions. - These sub-steps are retried until the deployment succeeds: - Depending on the provider (ARM, Bicep, or Terraform) a deployment is tried - If the Service Principal does not have sufficient permissions, an authorization error is returned by the deployment. If authorization errors have occurred, they are parsed to fetch the missing scopes and permissions. The [authorizationErrorParser Tests](./pkg/domain/authorizationErrorParser_test.go) provide details of the different kinds of authorization errors typically received. - The missing permissions are added to the custom role. - The missing permissions are added to the result. - Once no authorization error is received, the utility prints the permissions assigned to the Service Principal. - The required permissions are displayed based on the display options. These options can be used to view the resource-wise breakup of permissions and also to export the result in JSON format. - All resources created are cleaned up by the utility, including the Role Assignments and Custom Role. ## Supported Deployment Providers - Azure **ARM** Template: Uses ARM deployment endpoint in Incremental mode to get the authorization errors and find the minimum permissions required for a deployment. Resources are actually created during the process and then automatically cleaned up. The ARM endpoints return multiple authorization errors at a time, but since resources are actually deployed, the execution time can range from several minutes to longer depending on the complexity of the template and resources being deployed. > [!NOTE] > The previous what-if analysis mode (which completed in ~90 seconds) has been deprecated due to incomplete permission detection in some scenarios.* - **Bicep**: The Bicep mode uses ARM deployment endpoint in Incremental mode to get the authorization errors and find the minimum permissions required for a deployment. Internally, the utility converts the Bicep file to an ARM template and then uses the ARM deployment endpoint. Like ARM mode, resources are actually created and automatically cleaned up, so execution time can range from several minutes to longer depending on template complexity. > [!NOTE] > The previous what-if analysis mode (which completed in ~90 seconds) has been deprecated due to incomplete permission detection in some scenarios.* - **Terraform**: The Terraform mode finds the minimum permissions required for a deployment by getting the authorization errors from the Terraform apply and destroy commands. All resources are cleaned up by the utility. > [!NOTE] > By default, when Terraform reports an "existing resource" error, MPF may import those resources into Terraform state to continue execution, and will then destroy the imported resources during cleanup. Use this tool in a dev/test environment. --- > [!NOTE] > ARM and Bicep are executed as resource-group scoped incremental deployments, and MPF will create and delete a temporary resource group during execution. ## AI-Assisted Analysis For AI-assisted analysis using GitHub Copilot CLI or similar tools, see [AGENTS.md](./AGENTS.md). This provides instructions for AI agents to automatically analyze IaC repositories and determine minimum permissions. **Use in your own repository:** Copy [AGENTS.md](./AGENTS.md) to your Azure IaC project, then run Copilot CLI: ```bash # Download to your project curl -sO https://raw.githubusercontent.com/Azure/mpf/main/AGENTS.md # Or for VS Code Copilot Chat mkdir -p .github && curl -s https://raw.githubusercontent.com/Azure/mpf/main/AGENTS.md -o .github/copilot-instructions.md # Run Copilot CLI copilot ``` **Example prompt:** > "Analyze this repository and find the minimum Azure permissions required to deploy the infrastructure" ## Flags and Environment Variables The commands can be used with flags or environment variables. For details on the flags and environment variables, please refer to the [command line flags and environment variables](docs/commandline-flags-and-env-variables.md) document. ## Installation / Quickstart For installation instructions, please refer to the [installation and quickstart](docs/installation-and-quickstart.md) document. ## Usage Details For usage details, please refer to the [quickstart / usage details](docs/installation-and-quickstart.md#quickstart--usage) document. ## Display Options To view details of the display options the utility provides, please refer to the [display options](docs/display-options.MD) document. ## Building Locally You can also build locally by cloning this repo and running `task build`. ## Testing Locally ### Unit Tests To run the unit tests, run `task testunit`. ### End to End ARM Tests To run the end-to-end tests for ARM, you need to have the following environment variables set, and then execute `task teste2e:arm`: ```shell # bash export MPF_SUBSCRIPTIONID="YOUR_SUBSCRIPTION_ID" export MPF_TENANTID="YOUR_TENANT_ID" export MPF_SPCLIENTID="YOUR_SP_CLIENT_ID" export MPF_SPCLIENTSECRET="YOUR_SP_CLIENT_SECRET" export MPF_SPOBJECTID="YOUR_SP_OBJECT_ID" ``` ```powershell # powershell $env:MPF_SUBSCRIPTIONID="YOUR_SUBSCRIPTION_ID" $env:MPF_TENANTID="YOUR_TENANT_ID" $env:MPF_SPCLIENTID="YOUR_SP_CLIENT_ID" $env:MPF_SPCLIENTSECRET="YOUR_SP_CLIENT_SECRET" $env:MPF_SPOBJECTID="YOUR_SP_OBJECT_ID" ``` ```shell task teste2e:arm ``` ### End to End Bicep Tests To run the end-to-end tests for Bicep, you need to have the following environment variables set, and then execute `task teste2e:bicep`: ```shell # bash export MPF_SUBSCRIPTIONID="YOUR_SUBSCRIPTION_ID" export MPF_TENANTID="YOUR_TENANT_ID" export MPF_SPCLIENTID="YOUR_SP_CLIENT_ID" export MPF_SPCLIENTSECRET="YOUR_SP_CLIENT_SECRET" export MPF_SPOBJECTID="YOUR_SP_OBJECT_ID" export MPF_BICEPEXECPATH="/opt/homebrew/bin/bicep" # Path to the Bicep executable ``` ```powershell # powershell $env:MPF_SUBSCRIPTIONID="YOUR_SUBSCRIPTION_ID" $env:MPF_TENANTID="YOUR_TENANT_ID" $env:MPF_SPCLIENTID="YOUR_SP_CLIENT_ID" $env:MPF_SPCLIENTSECRET="YOUR_SP_CLIENT_SECRET" $env:MPF_SPOBJECTID="YOUR_SP_OBJECT_ID" $env:MPF_BICEPEXECPATH=$(where.exe bicep) ``` ```shell task teste2e:bicep ``` ### End to End Terraform Tests The Terraform end-to-end tests can take a long time to execute, depending on the resources being created. To run the end-to-end tests for Terraform, you need to have the following environment variables set, and then execute `task teste2e:terraform`: ```shell # bash export MPF_SUBSCRIPTIONID="YOUR_SUBSCRIPTION_ID" export MPF_TENANTID="YOUR_TENANT_ID" export MPF_SPCLIENTID="YOUR_SP_CLIENT_ID" export MPF_SPCLIENTSECRET="YOUR_SP_CLIENT_SECRET" export MPF_SPOBJECTID="YOUR_SP_OBJECT_ID" export MPF_TFPATH=$(which terraform) # Path to the Terraform executable ``` ```powershell # powershell $env:MPF_SUBSCRIPTIONID="YOUR_SUBSCRIPTION_ID" $env:MPF_TENANTID="YOUR_TENANT_ID" $env:MPF_SPCLIENTID="YOUR_SP_CLIENT_ID" $env:MPF_SPCLIENTSECRET="YOUR_SP_CLIENT_SECRET" $env:MPF_SPOBJECTID="YOUR_SP_OBJECT_ID" $env:MPF_TFPATH=$(where.exe terraform) ``` ```shell task teste2e:terraform ``` ## Permissions required by default Azure CLI credentials The default Azure CLI credentials used by the utility need to have the following permissions: - `Microsoft.Authorization/roleDefinitions/read` - `Microsoft.Authorization/roleDefinitions/write` - `Microsoft.Authorization/roleDefinitions/delete` - `Microsoft.Authorization/roleAssignments/read` - `Microsoft.Authorization/roleAssignments/write` - `Microsoft.Authorization/roleAssignments/delete` - `Microsoft.Resources/subscriptions/resourcegroups/delete` - `Microsoft.Resources/subscriptions/resourcegroups/read` - `Microsoft.Resources/subscriptions/resourcegroups/write` ## Known Issues and Workarounds The [Known Issues and Workarounds](docs/known-issues-and-workarounds.MD) document provides details on the known issues and workarounds for the utility. ## MPF Design The [MPF Design](docs/mpf-design.md) document provides details on the design, including the packages and abstractions. ## License This project is under an [MIT License](LICENSE). ## 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](https://opensource.microsoft.com/codeofconduct/). For more information, see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [opencode@microsoft.com](mailto: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](https://www.microsoft.com/en-us/legal/intellectualproperty/trademarks/usage/general). 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 parties' policies.
