Create a Project

Create a project when you want to group nodes under a shared set of policies and deployment rules. You can create a project before onboarding any nodes, or during the onboarding flow when prompted to assign a project. Open Infrastructure > Fleet > Projects, then select the contextual + create action in the lower-right corner. The project creation wizard has three steps for Standard projects: entering project details, selecting policies, and reviewing before adding. Deployment type projects have an additional step between details and policies to configure the deployment.

Before You Start

You have the SysManager or SysAdmin role in your enterprise. See Manage Roles.
Decide whether to use the Standard or Deployment project type before you begin. See Projects for a comparison.
Plan the policies you want to attach. Once nodes join the project, those policies apply automatically.

Enter the Project Details

Enter the project’s basic information and settings.

Field	Description
Name	Unique identifier for the project within the enterprise. Cannot be changed after creation.
Title	Display label for the project. Can be changed after creation.
Description	Optional free-text to help you and other administrators recall the purpose of the project.
Type	Select Standard or Deployment. See Projects for guidance on which type to use.
Profile	Select Regular or Azure. If you select Deployment as the type, this field is automatically set to Regular and cannot be changed.
Tags	Key-value pairs you can assign to the project. Tags on the project can match tags on edge apps so that the app is automatically associated with the correct project. Tags also enable role scope: a role scoped to a project tag applies only to projects that carry that tag. For example, tag a project `region:eu` to restrict any role scoped to `region:eu` to this project only. See Tagging.
Network Flow Log	When enabled, collects metadata for all network flows generated by application instances, including source and destination IP addresses and ports, applied ACL rules, and packet counters.
Interface Ordering	When enabled, keeps the adapter order of application instances consistent across nodes. EVE-OS (Edge Virtualization Engine) presents an instance’s network adapters in the same order on every node it deploys to. You can set the order of an instance’s interfaces yourself, or let Edge Infrastructure Services assign one. An order where two interfaces claim the same position is rejected. Requires EVE-OS 13.8.0 or greater on the nodes. See Interface Ordering for Application Instances.
Suppress Streaming Telemetry	When enabled, prevents the node from streaming telemetry data to Edge Infrastructure Services.

If you select the Azure profile, additional fields appear for Azure Active Directory credentials (App ID, App Password, Tenant ID), Device Provisioning Service (DPS) configuration, IoT Hub name, resource group, and optional X.509 certificate-based authentication for leaf devices. Select Next to continue.

Configure the Deployment

This step applies to Deployment type projects only. Standard type projects skip directly to the Policies step.

Field	Description
Deployment Identifier	Unique identifier for the deployment within the enterprise. You assign this identifier to nodes so that they receive this deployment’s configuration. Required.
Deployment Tag	The tag name attached to nodes to associate them with this deployment. Nodes tagged with this name receive the deployment’s node, network, app, and volume policies. Required. See Tagging.

Both fields are required before you can continue. Select Next to continue.

Select the Project Policies

Select the checkbox next to each policy type you want to include in the project. The policies offered depend on the project type:

Standard and Azure IoT projects can include Node Policy, Virtual Networks Policy, Edge Apps Policy, Edge View Policy, and Edge Sync Policy.
Deployment projects can include Node Policy, Virtual Networks Policy, Edge Apps Policy, Edge View Policy, and Volume Instances Policy.

Edge Sync Policy is not available on Deployment projects, and Volume Instances Policy is not available on Standard or Azure IoT projects. For field-level details on each policy type, see Configure Project Policies. Select Next after making your selections.

Review and Create the Project

Review the project configuration summary before creating the project. The summary displays the project name, title, type, attestation mode, configuration lock status, network flow log setting, interface ordering setting, suppress streaming telemetry setting, and the count of enabled policies. Deployment projects also show the deployment identifier and the deployment tag. Select Create Project to create the project. On a Deployment project the button reads Create Deployment. To make changes, navigate back to any earlier step.

Next Steps

Configure Project Policies

Field-level detail on each policy type.

Manage Projects

View, update, or delete projects.

Onboard nodes

Assign nodes to the new project.

Tagging

Tag projects to enable role scope, restricting a role to projects that carry specific tags.

Start Here

Infrastructure Services Overview

Core infrastructure

Build

Applications and delivery

Edge Kubernetes

Operations

Monitor

Administration and Security

Troubleshooting

Partnerships

Before You Start

Enter the Project Details

Configure the Deployment

Select the Project Policies

Review and Create the Project

Next Steps

Configure Project Policies

Manage Projects

Onboard nodes

Tagging

​Before You Start

​Enter the Project Details

​Configure the Deployment

​Select the Project Policies

​Review and Create the Project

​Next Steps

Configure Project Policies

Manage Projects

Onboard nodes

Tagging

Before You Start

Enter the Project Details

Configure the Deployment

Select the Project Policies

Review and Create the Project

Next Steps