I created ADLA and ADLS accounts, but not able to access the connected ADLS from ADLA

Hi @Pranav Agrawal
Thankyou for reaching microsoft Q&A!

One important point to verify is whether the storage account you're trying to connect is Azure Data Lake Storage Gen1 or Gen2. Azure Data Lake Analytics (ADLA) only supports Azure Data Lake Storage Gen1 accounts. If you're using an ADLS Gen2 account (Storage Account with Hierarchical Namespace enabled), it will not appear as a connected data source in the ADLA portal, and jobs may fail to access the storage.

If you're using ADLS Gen1, please check the following:

• Confirm the Data Lake Store account has been added under Data Lake Store Accounts in your ADLA account.

Verify that your user account has the necessary permissions on both the ADLA and ADLS resources. If the storage account was created after the ADLA account, try removing and re-adding the Data Lake Store account association.

For reference:

Azure Data Lake Analytics overview: https://learn.microsoft.com/azure/data-lake-analytics/data-lake-analytics-overview Manage Data Lake Store accounts for ADLA: https://learn.microsoft.com/azure/data-lake-analytics/data-lake-analytics-manage-use-portal ADLS Gen1 documentation: https://learn.microsoft.com/azure/data-lake-store/

If the issue persists, could you share the exact error message when submitting a job and confirm whether the storage account is Gen1 or Gen2? That will help narrow down the cause.

Hi Pranav,

The main thing to check here is whether you are using Azure Data Lake Analytics (ADLA) with ADLS Gen1 or ADLS Gen2.

Azure Data Lake Analytics was designed around the older Data Lake Store/ADLS Gen1 model, and the ADLA service itself has also been retired. Because of that, the experience in the Azure portal may not behave like a normal active service anymore, and you may not be able to submit jobs or browse/list the connected storage account from the ADLA portal.

If you created a newer ADLS account, it is most likely ADLS Gen2. In that case, I would not expect it to work correctly with ADLA job submission from the portal.

A few things to verify:

1. Confirm whether the storage account is ADLS Gen1 or ADLS Gen2.

Confirm whether the ADLA account and the storage account are in the same subscription/tenant and supported region.

Check whether the ADLA account has the storage account added as a linked data source.

Check permissions on the storage account. The user submitting the job needs access to the ADLA account and the storage path.

If this is a new setup, consider moving to a supported service instead of ADLA.

For new development, the better option is to use one of the currently supported services, such as:

Azure Synapse Analytics Spark

Azure Databricks

Microsoft Fabric

Azure Data Factory / Synapse pipelines for orchestration and data movement

So in short, if this is a newly created ADLA/ADLS setup, the issue is most likely due to the ADLA retirement / unsupported combination rather than a simple portal configuration problem. I would recommend using ADLS Gen2 with Synapse, Databricks, Fabric, or ADF instead of trying to build a new workload on ADLA.Hi Pranav,

The main thing to check here is whether you are using Azure Data Lake Analytics (ADLA) with ADLS Gen1 or ADLS Gen2.

Azure Data Lake Analytics was designed around the older Data Lake Store/ADLS Gen1 model, and the ADLA service itself has also been retired. Because of that, the experience in the Azure portal may not behave like a normal active service anymore, and you may not be able to submit jobs or browse/list the connected storage account from the ADLA portal.

If you created a newer ADLS account, it is most likely ADLS Gen2. In that case, I would not expect it to work correctly with ADLA job submission from the portal.

A few things to verify:

Confirm whether the storage account is ADLS Gen1 or ADLS Gen2.

Confirm whether the ADLA account and the storage account are in the same subscription/tenant and supported region.

Check whether the ADLA account has the storage account added as a linked data source.

Check permissions on the storage account. The user submitting the job needs access to the ADLA account and the storage path.

If this is a new setup, consider moving to a supported service instead of ADLA.

For new development, the better option is to use one of the currently supported services, such as:

Azure Synapse Analytics Spark

Azure Databricks

Microsoft Fabric

Azure Data Factory / Synapse pipelines for orchestration and data movement

So in short, if this is a newly created ADLA/ADLS setup, the issue is most likely due to the ADLA retirement / unsupported combination rather than a simple portal configuration problem. I would recommend using ADLS Gen2 with Synapse, Databricks, Fabric, or ADF instead of trying to build a new workload on ADLA.