Skip to content

Commit

Permalink
Deployed 52246ae with MkDocs version: 1.4.2
Browse files Browse the repository at this point in the history
  • Loading branch information
iknowjason committed Aug 21, 2024
1 parent edb42fb commit 2f58014
Show file tree
Hide file tree
Showing 4 changed files with 16 additions and 7 deletions.
1 change: 0 additions & 1 deletion CNAME

This file was deleted.

20 changes: 15 additions & 5 deletions install/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -939,11 +939,21 @@ <h4 id="option-2-create-an-azure-service-principal">Option 2: Create an Azure S
</ul>
<p>For building the Azure infrastructure resources, assigning the Service Principal a role of <code>Owner</code> can help as well.</p>
<p><strong>Important Note:</strong> The Sentinel generator requires a special permission that adds an Entra ID diagnostic setting. If you want to use the <code>sentinel.py</code> generator and you are using a Service Principal, you need to add a special permission to the Service Principal you are using with terraform:</p>
<p>Adding this diagnostic setting (for Entra ID logging to Log Analytics Workspace) requires special privileges for your terraform Service Principal to have authorized to read and write changes to aadiam resources (Azure Diagnostic Settings). You must add a special role to your SP. You can let terraform run and it will show an error. You can simply comment out this resource temporarily.
1. Ensure that owner permissions are added for the SP
2. Ensure that SP has Global Administrator permissions
3. Get the <code>object_id</code> of your terraform service principal. You can get this from the Azure portal or by looking at the error returned by terraform.
4. Run this command while logged in as global admin with <strong>az login</strong>, changing the <code>SP_OBJECT_ID</code> to be your terraform Service Principal's <code>object_id</code>. The <code>--role ID</code> is for owner role which you should have added for your SP in step 1.</p>
<p>Adding this diagnostic setting (for Entra ID logging to Log Analytics Workspace) requires special privileges for your terraform Service Principal to have authorized to read and write changes to aadiam resources (Azure Diagnostic Settings). You must add a special role to your SP. You can let terraform run and it will show an error. You can simply comment out this resource temporarily.</p>
<ol>
<li>
<p>Ensure that owner permissions are added for the SP</p>
</li>
<li>
<p>Ensure that SP has Global Administrator permissions</p>
</li>
<li>
<p>Get the <code>object_id</code> of your terraform service principal. You can get this from the Azure portal or by looking at the error returned by terraform.</p>
</li>
<li>
<p>Run this command (below) while logged in as global admin with <strong>az login</strong>, changing the <code>SP_OBJECT_ID</code> to be your terraform Service Principal's <code>object_id</code>. The <code>--role ID</code> is for owner role which you should have added for your SP in step 1.</p>
</li>
</ol>
<pre><code class="language-commandline">az role assignment create --assignee-principal-type ServicePrincipal --assignee-object-id &lt;SP_OBJECT_ID&gt; --scope &quot;/providers/Microsoft.aadiam&quot; --role b24988ac-6180-42a0-ab88-20f7382dd24c
</code></pre>
<h3 id="step-4-generate-terraform">Step 4: Generate Terraform</h3>
Expand Down
2 changes: 1 addition & 1 deletion search/search_index.json

Large diffs are not rendered by default.

Binary file modified sitemap.xml.gz
Binary file not shown.

0 comments on commit 2f58014

Please sign in to comment.