Skip to content

Deploy Copilot for Security

Automated Deployment

Deploy to Azure

Manual Deployment (via Template Spec)

Create a Template Spec

  1. Login to Azure Portal: If you haven't already, sign in to the Azure Portal.
  2. Search for Template Spec: In the portal, use the search bar to look for "Template specs."
  3. Create New Template Spec:
  4. Click on "Create Template Spec."
  5. Choose the template version and click on "Edit Template."
  6. Build the Basics and Set a Version Number:
  7. Provide the necessary information for the template creation.
  8. Ensure you set a meaningful version number for tracking changes.
  9. In Edit Template, Paste Code Below, Changing the Default Value to requirements:
  10. Customize your template spec by adding the necessary resources and configurations.
  11. In the template editor, paste your ARM template code.
  12. Modify any default values as needed to match your requirements.
  13. Click Save: Save your changes to the template spec.
  14. Tag your Template: Add relevant tags to your template spec for better organization and searchability.
  15. Review + Create:
  16. Double-check your settings and details.
  17. Finally, create the template spec.

Deploy a Template Spec

  1. Login to Azure Portal: If you haven't already, sign in to the Azure Portal.
  2. Search for Template Spec: In the portal, use the search bar to look for "Template specs."
  3. Select your Template Spec File: Click on the Template you recently created.
  4. Deploy Template Spec:
  5. Select 'Deploy'
  6. Confirm the Template Details
  7. Select 'Review + Create'
  8. Click 'Create'

Change the Default Values:

  • capacityName
  • This name must be unique and contain only lowercase letters and numbers with no spaces.
  • location
  • Needs to Reference the Geo Region
    • ANZ - australiaeast
    • US - eastus
    • EU - westeurope
    • UK - uksouth
  • numberOfUnits
  • Security compute units provide the computing power that drives the Security Copilot experience (USD 4 per unit).
  • Numeric Value of the amount of SCU to provision
  • crossGeoCompute
  • If this location is busy, allow Copilot to evaluate prompts anywhere in the world (recommended for optimal performance)
  • Allowed Values: "Allowed", "NotAllowed"
  • geo
  • This selection will affect where your prompts are evaluated and how your usage is priced.
  • Allowed Values: "ANZ", "US", "UK", "EU"
{
    "$schema": "http://schema.management.azure.com/schemas/2014-04-01-preview/deploymentTemplate.json",
    "contentVersion": "1.0.0.0",
    "parameters": {
        "capacityName": {
            "type": "string",
            "defaultValue": "copilotcompute"
        },
        "location": {
            "type": "string",
            "defaultValue": "australiaeast",
            "allowedValues": [
                "australiaeast",
                "eastus",
                "westeurope",
                "uksouth"
            ]
        },
        "numberOfUnits": {
            "type": "int",
            "defaultValue": 1
        },
        "crossGeoCompute": {
            "type": "string",
            "defaultValue": "NotAllowed",
            "allowedValues": [
                "NotAllowed",
                "Allowed"
            ]
        },
        "geo": {
            "type": "string",
            "defaultValue": "ANZ",
            "allowedValues": [
                "ANZ",
                "US",
                "UK",
                "EU"
            ]
        }
    },
    "resources": [
        {
            "apiVersion": "2023-12-01-preview",
            "name": "[parameters('capacityName')]",
            "location": "[parameters('location')]",
            "type": "Microsoft.SecurityCopilot/capacities",
            "properties": {
                "numberOfUnits": "[parameters('numberOfUnits')]",
                "crossGeoCompute": "[parameters('crossGeoCompute')]",
                "geo": "[parameters('geo')]"
            }
        }
    ]
}

Benefits of Using Template Specs

  1. Standardization: You can use standard ARM templates for your template spec, ensuring consistency across deployments.
  2. Access Management: Instead of using SAS tokens, you manage access through Azure RBAC (Role-Based Access Control). Users can deploy the template spec without needing write access to the template itself.
  3. Integration: You can seamlessly integrate the template spec into existing deployment processes, such as PowerShell scripts or DevOps pipelines.
  4. Sharing and Collaboration: Template specs allow you to create canonical templates and share them with teams in your organization. They're secure because they're available for deployment by Azure Resource Manager, but not directly accessible to users without the correct permissions .

Disclaimer: Please be aware that the logic apps provided are examples intended for use with Copilot for Security. Users are encouraged to customize these samples to meet their specific requirements. These should serve as guidelines and inspiration for creating tailored logic apps for ones own use

Technical Disclaimer: Logic Apps, SCU Usage, and Best Practices

Attention Customers!

When utilizing Logic Apps on Copilot, please be aware that it may result in increased consumption of Secure Compute Units (SCUs). We recommend closely monitoring SCU usage to optimize resource management.