Blueprint Workspace
The workspace enables you to create and configure your blueprint. This includes adding available resources, Apps, services and connectivity requirements, and configuring their settings for the blueprint. You can also view or update the blueprint's properties (depending on your permissions).
Navigating the blueprint workspace
In the image below, hover over an area or option to learn more about it, or use the table that follows.

Blueprint Diagram view
Diagram view is the default view for the blueprint. It enables you to add and arrange elements in your blueprint, such as resources and Apps, define connectivity requirements between these elements, and set the blueprint's properties, including description, image, blueprint categories, orchestration, instructions and inputs.
In Diagram view you can also view blueprint and resource commands.
Tip: To move or delete multiple elements at once, hold down the [Ctrl] key, select the elements and perform the suitable action.
Blueprint List view
List view displays the blueprint's elements and their sub-resources in a list.
For more information, see Blueprint List View.
Reserving a blueprint from the blueprint workspace
When reserving a blueprint, you can define certain properties of the sandbox and may need to provide information for resource provisioning and automation processes.
If there's a resource or scheduling conflict, CloudShell will offer available time slots for the sandbox. For additional information about sandboxes and reservation conflicts, see Creating Sandboxes.
Note: Blueprints of type ‘view’ cannot be reserved.
To create an immediate or future sandbox:
-
In the Blueprint Catalog, on the required blueprint tile, click Reserve. Alternatively, in the blueprint workspace, click the Reserve button.
The Reserve dialog box is displayed.
Note: The timezone for the sandbox is indicated in the title of the Reserve dialog box.
-
If the blueprint is defined as a persistent blueprint, select the Sandbox Type you want to deploy:
- Regular Sandbox to spin up a time-limited sandbox
- Persistent Sandbox to deploy a persistent sandbox with no end time. For details, see Persistent Sandboxes Overview.
-
In the Schedule field, you can set the required sandbox duration or specify the explicit start and/or end time. Use the Calendar button to set future dates.
- Most of the scheduling options are disabled for persistent blueprints.
- For non-persistent sandboxes, if a maximum duration was set for the sandbox, the user will not be able to reserve for a duration beyond this setting.
-
(Unavailable for persistent blueprints) To have this sandbox repeat in a series, click Add Recurrence. If this option is missing, the admin needs to enable it using the
EnableRecurringReservation
key.The Recurrence page is displayed.
- To have the sandbox repeat on specific days, click the Pattern field and either select the days or select Daily to have the sandbox repeat on all days of the week.
- In the Range field, define the period in which the sandbox will repeat.
-
Optionally, change the Name of the sandbox. By default, the new sandbox name is the blueprint name.
Note: The sandbox’s name has a limit of 60 characters.
- In the Blueprint field, you can see the blueprint on which the sandbox is based.
-
To specify additional options, click the Advanced Form
button.
The advanced form enables you to configure the email notifications, permissions and other options.
- Optionally, enter a Description. Otherwise, the description of the sandbox will default to the blueprint description.
-
To define an owner for the sandbox, click the Owner and select the required user. By default, the user who initiated the scheduling action is set as the sandbox owner.
-
Instead of changing the owner of the sandbox, you can permit additional users to use the sandbox. Click the Permitted Users section and select the users you wish to add.
- To prevent users from ending the sandbox before its scheduled end time, enable Termination Protection. This option ensures your sandbox isn't ended accidentally or prematurely. And when you are ready to manually end the sandbox, disable the option in the sandbox's properties window and then end it.
-
You can configure CloudShell to send email notifications to the owner of the sandbox and permitted users.
Note: This capability requires the administrator to activate the email notifications feature using the
ReservationEmail
configuration keys.-
Click the Email Notifications field.
The Email Notifications area expands.
-
Configure the email notification settings.
- On start - Sends notification as the sandbox starts.
- On setup complete - Sends notification when the sandbox setup completes.
- Before end - (Unavailable for persistent blueprints) Sends notification before the Teardown process begins. The exact time is decided by the user.
- On end - Sends when the sandbox ends.
-
-
If the blueprint has inputs (global inputs, published abstract resource or service inputs), you will be asked to provide them.
Tip: To expand the value area, click and drag down the icon in the bottom right corner of the frame.
-
Click Reserve.
The sandbox is being reserved.
If you are reserving a blueprint that has the Default Sandbox Setup script, the script runs, and an indication next to the sandbox state informs you of its progress.More...
If any resource is unavailable for the scheduled time slot, the Conflicts dialog box is displayed, proposing an alternative time slot, as described in Dealing with conflicts.
The new sandbox is displayed in Diagram view with a blue Sandbox label at the top of the canvas and a green Active icon in the toolbar:
Note: For persistent blueprints, the blue Sandbox label is replaced with a Persistent Environment label.
If you have a license for the Save and Restore paid add-on, you will see a Save Sandbox button. For more information, see the Sandbox Save and Restore Overview.