Skip to content

Commit a49bf8d

Browse files
committed
Remove outdated callout
1 parent 229693a commit a49bf8d

File tree

1 file changed

+0
-9
lines changed

1 file changed

+0
-9
lines changed

articles/notebooks/configure-manage-azure-notebooks-projects.md

Lines changed: 0 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -60,15 +60,6 @@ To create a new DSVM instance, follow the instructions on [Create an Ubuntu Data
6060
>
6161
> ![Shutdown button in Azure Notebooks](media/shutdown.png)
6262
63-
> [!IMPORTANT]
64-
> When using different virtual machines, the notebooks you run on them must be entirely self-contained. At present, Azure Notebooks copies only the *.ipynb* file to the VM but doesn't copy any other files in the project. As a result, notebooks running on other VMs fail to find other project files.
65-
>
66-
> You can work around this behavior in two ways:
67-
>
68-
> 1. Copy project files manually to the VM.
69-
>
70-
> 2. Embed the files within a setup notebook that you run first before the primary notebook. In the setup notebook, create a code cell for each file where the cell contains the file contents. Then at the top of each cell, insert the command `%writefile <filename>`, where `<filename>` is the name of the file to receive the contents. When you run the notebook, it creates all those files on the VM. For an example, see the [setup.ipynb file in the Microsoft Pet Detector demo](https://github.com/microsoft/connect-petdetector) (GitHub).
71-
7263
## Edit project metadata
7364

7465
On the project dashboard, select **Project Settings**, then select the **Information** tab, which contains the project's metadata as described in the following table. You can change project metadata at any time.

0 commit comments

Comments
 (0)