Skip to main content
A project is a logical grouping of nodes and the policies that govern them. When a node joins a project, the policies defined in that project are automatically applied: virtual networks, edge app deployments, volume instances, attestation requirements, and more. This lets you manage large fleets of nodes consistently without configuring each node individually. In the Edge Intelligence Platform Console, open Infrastructure > Fleet > Projects to view, create, and manage your projects.

​
Before You Start

The maximum number of projects you can create is controlled by your enterprise entitlements.

​
Project Types and Profiles

Selecting the right project type determines which policies are available and how deployments are structured. The policy sets differ because the two types store their policies in different places. A Standard project holds its policies on the project itself, so you configure them once and every node that joins the project receives them. A Deployment project holds its policies on each deployment record, so a single project can carry several policy sets and a node receives the one whose tag it matches. Use Standard for simpler setups, including Azure IoT Hub integrations. Use Deployment for tiered deployments where multiple edge apps must roll out to a fleet. For Azure IoT Hub setup and configuration, see Azure Integration.

​
Zero-Touch Deployments

Zero-Touch Deployments (ZTD) is the mechanism that makes project policies act automatically on your nodes. When you onboard a new node and assign it to a project, the tags on that node are matched to the deployment tags defined in the project. Matching policies and applications are applied to the node automatically, without further manual configuration. ZTD is the primary reason to use the Deployment project type. In a Deployment project, you define one or more deployment configurations, each with a set of tags. When a node’s tags match a deployment’s tags, the deployment’s network configurations, volume instances, and applications are applied to that node. To update which deployment applies to a node, change the node’s tags to match the target deployment. Edge Infrastructure Services handles the transition automatically. ZTD also supports versioned rollouts. A project can hold up to 100 deployment versions. To roll back, update the node’s deployment tag to match the tag of the previous deployment version. To set up the policies that ZTD applies to matching nodes, see Configure Project Policies.

​
Tagging

Tags are key-value pairs you assign to resources in Edge Infrastructure Services. The key and value are both strings you define, for example env:production, region:emea, or tie-breaker:true. Tags let you classify, filter, and automate across your infrastructure without changing how resources are configured. Tags are used throughout the project and deployment system: Consistent use of tags across your fleet reduces manual configuration and makes large deployments manageable. Plan your tagging scheme before creating projects and deployments so that policy assignments work correctly when nodes join. See Tagging.

​
In This Section

  • Create a Project: Step through the creation wizard to define project details, deployments, and settings.
  • Configure Project Policies: Configure the node, virtual networks, edge app, Edge View, and Edge Sync policies that govern nodes in the project.
  • Manage Projects: View the project list, navigate the detail page, update project settings, and delete projects.