diff --git a/docs/integrations/azure_repos_app.md b/docs/integrations/azure_repos_app.md
index ca678183..4b33b3ab 100644
--- a/docs/integrations/azure_repos_app.md
+++ b/docs/integrations/azure_repos_app.md
@@ -33,7 +33,7 @@ There are two key benefits of using the Azure Repos App over manual CI/CD integr
 
 6. During setup, Infracost will need a short-lived Personal Access Token (PAT) with additional permissions to do the following. The PAT can be deleted in Azure Repos after the setup is done.
    - Create an Azure Active Directory (AAD) group that can manage service hooks and branch policies.
-   - Add the Infracost service principal to this group.
+   - Add the Infracost service principal to this group. The Azure DevOps Access Level for the Infracost service principal needs to be "Basic" (not the free Stakeholder one) so it has permission to list repos.
    - Add selected projects to this group so Infracost can manage webhooks and policies in those projects.
    Ensure that the short-lived PAT belongs to an Owner or Project Collection Administrator and has the following scopes:
       - **Graph (Read & Manage)** - to create the Infracost group.
diff --git a/docs/integrations/github_app.md b/docs/integrations/github_app.md
index 3d421fb3..f71969e0 100644
--- a/docs/integrations/github_app.md
+++ b/docs/integrations/github_app.md
@@ -99,17 +99,11 @@ The GitHub App automatically reflects the following changes in Infracost:
 
 From the Org Settings > Integrations > GitHub App page, you can disable pull request comments so cost estimates, guardrails and tagging policies are only shown in Infracost Cloud. This enables you to test these features without impacting engineering workflows.
 
-### GitHub Actions to App migration
-
-1. Follow the [usage](#usage) docs to install the app. You can do this from the same Infracost organization you use already, and going into the Org Settings > Integrations page.
-2. Test it by [sending a pull request](/docs/infracost_cloud/get_started/#4-send-a-pull-request).
-3. Remove all Infracost steps from your GitHub Actions.
-
 ### Dismissing policy issues
 
 Infracost FinOps and Tagging issues can be dismissed directly from the GitHub pull request UI, even if the policy is set to block pull requests. This allows engineers to ship critical changes without having to fix all issues. During non-emergency circumstances, we recommend engineers fix the issues they can, and dismiss any that they cannot fix.
 
-Any GitHub pull request comment will contain information on how to dismiss the issues. 
+GitHub pull request comments contain information on how to dismiss issues.
 
 <img src={useBaseUrl("img/github/desc.png")} alt="pr comment" />
 
@@ -127,3 +121,9 @@ Dismissing a policy issue works as follows:
   <img src={useBaseUrl("img/github/checks.png")} alt="checks" />
 - Dismissed issues are shown in Infracost Cloud in the policies pages. You can filter by dismissed issues to see all the issues your engineers have dismissed and their reasons.
   <img src={useBaseUrl("img/github/dismissed-table.png")} alt="dismissed table" />  
+
+### GitHub Actions to App migration
+
+1. Follow the [usage](#usage) docs to install the app. You can do this from the same Infracost organization you use already, and going into the Org Settings > Integrations page.
+2. Test it by [sending a pull request](/docs/infracost_cloud/get_started/#4-send-a-pull-request).
+3. Remove all Infracost steps from your GitHub Actions.
diff --git a/src/components/Navbar.js b/src/components/Navbar.js
index 24ad6898..a80a93b1 100644
--- a/src/components/Navbar.js
+++ b/src/components/Navbar.js
@@ -108,6 +108,10 @@ function Navbar({ isDocs }) {
           label: 'FinOps Glossary',
           href: '/glossary/',
         },
+        {
+          label: 'FinOps Policies',
+          href: '/finops-policies/',
+        },
         {
           label: 'Blog',
           href: '/blog/',