issues encountered during the Azure Storage SAS module on Microsoft Learn

Here's a summary of the issues encountered during the Azure Storage SAS module on Microsoft Learn (https://video2.skills-academy.com/en-us/training/modules/control-access-to-azure-storage-with-sas/4-exercise-use-shared-access-signatures?tryIt=true):

Issues Encountered with Azure Storage SAS Module

SDK Version Mismatch:

• The module's project is configured to use .NET SDK version 7.0, but only .NET SDK version 8.0 was available in the environment. This caused the application to fail when attempting to run the project.

Outdated or Vulnerable Packages:

  - Several warnings were generated due to known vulnerabilities in the `Azure.Identity` package (version 1.10.1). These vulnerabilities should be addressed, and the module could benefit from updating to more secure package versions.
  
  **Repository Cloning Issues**:
  
     - An error occurred during the `git clone` step because the destination directory (`sas`) already existed and wasn't empty. This could happen if the user accidentally runs the clone command multiple times or if previous attempts weren't properly cleaned up.
     
     **Credential Warnings in Azure CLI**:
     
        - While running commands with Azure CLI to create storage accounts and upload blobs, there were warnings about missing credentials (like connection strings or SAS tokens). Although the commands succeeded by automatically querying for account keys, it could be confusing for users who are not familiar with Azure CLI's behavior.
        
        **Framework Version Requirement**:
        
           - The application explicitly required .NET 7.0 to run, which wasn't installed in the environment. This could lead to frustration as the user either needs to install the required SDK or modify the project to work with the available .NET version.
           

Suggestions for Improvement

Update the Module: Consider updating the module to use the latest .NET SDK version (e.g., .NET 8.0) to ensure compatibility with current environments.

Address Security Vulnerabilities: Ensure that the project dependencies are up to date to avoid security vulnerabilities, especially in critical packages like Azure.Identity.

Improve Documentation: Provide clear guidance on handling situations where the repository might already exist or when credential warnings appear, helping users navigate potential issues more smoothly.

Streamline SDK Requirements: Either ensure the required SDK version is installed in the environment or adjust the project settings to match the most commonly available SDK versions.

This summary should help communicate the challenges faced during the exercise, offering constructive feedback for improving the module on Microsoft Learn.

4oHere's a summary of the issues encountered during the Azure Storage SAS module on Microsoft Learn:

Issues Encountered with Azure Storage SAS Module

SDK Version Mismatch:

• The module's project is configured to use .NET SDK version 7.0, but only .NET SDK version 8.0 was available in the environment. This caused the application to fail when attempting to run the project.

Outdated or Vulnerable Packages:

  - Several warnings were generated due to known vulnerabilities in the `Azure.Identity` package (version 1.10.1). These vulnerabilities should be addressed, and the module could benefit from updating to more secure package versions.
  
  **Repository Cloning Issues**:
  
     - An error occurred during the `git clone` step because the destination directory (`sas`) already existed and wasn't empty. This could happen if the user accidentally runs the clone command multiple times or if previous attempts weren't properly cleaned up.
     
     **Credential Warnings in Azure CLI**:
     
        - While running commands with Azure CLI to create storage accounts and upload blobs, there were warnings about missing credentials (like connection strings or SAS tokens). Although the commands succeeded by automatically querying for account keys, it could be confusing for users who are not familiar with Azure CLI's behavior.
        
        **Framework Version Requirement**:
        
           - The application explicitly required .NET 7.0 to run, which wasn't installed in the environment. This could lead to frustration as the user either needs to install the required SDK or modify the project to work with the available .NET version.
           

Suggestions for Improvement

Update the Module: Consider updating the module to use the latest .NET SDK version (e.g., .NET 8.0) to ensure compatibility with current environments.

Address Security Vulnerabilities: Ensure that the project dependencies are up to date to avoid security vulnerabilities, especially in critical packages like Azure.Identity.

Improve Documentation: Provide clear guidance on handling situations where the repository might already exist or when credential warnings appear, helping users navigate potential issues more smoothly.

Streamline SDK Requirements: Either ensure the required SDK version is installed in the environment or adjust the project settings to match the most commonly available SDK versions.

This summary should help communicate the challenges faced during the exercise, offering constructive feedback for improving the module on Microsoft Learn.