MICROSOFT APPLIED SKILL. Guided Project:
Published: 2024-06-20 22:47:56

This is exercise 2b of the Microsoft Applied skill guided project.

A. **CREATE A STORAGE ACCOUNT AND CONFIGURE HIGH AVAILABILITY**.
1.**Create a storage account for the internal private company documents.**
-  In the portal, search for and select Storage accounts.
-  Select + Create.
-  Select the Resource group created in the previous lab.
-  Set the Storage account name to private. Add an identifier to the name to ensure the name is unique.
-  Select Review, and then Create the storage account.
-  Wait for the storage account to deploy, and then select Go to resource.


![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/7ns7uzdlqqjasioz3kp5.png)

2.**This storage requires high availability if there’s a regional outage. Read access in the secondary region is not required. Configure the appropriate level of redundancy**.
- In the storage account, in the Data management section, select the
- Redundancy blade.
- Ensure Geo-redundant storage (GRS) is selected.
- Refresh the page.
- Review the primary and secondary location information.
- Save your changes.

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/vawm4s27b9qmnx0bddoj.png)

B. **CREATE A STORAGE CONTAINER, UPLOAD A FILE, AND RESTRICT ACCESS TO THE FILE**.
1.**Create a private storage container for the corporate data**.
- In the storage account, in the Data storage section, select the Containers blade.
-  Select + Container.
-  Ensure the Name of the container is private.
-  Ensure the Public access level is Private (no anonymous access).
-  As you have time, review the Advanced settings, but take the defaults.
-  Select Create.


![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/z6bsm46rtcp6ett980ps.png)

2. For testing, upload a file to the private container. he type of file doesn’t matter. A small image or text file is a good choice. Test to ensure the file isn’t publicly accessible.

-  Select the container.
-  Select Upload.
-  Browse to files and select a file.
-  Upload the file.
-  Select the uploaded file.
-  On the Overview tab, copy the URL.
-  Paste the URL into a new browser tab.
-  Verify the file doesn’t display and you receive an error.


![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/66uy78japcutjo7v5jfh.png)

3. An external partner requires read and write access to the file for at least the next 24 hours. Configure and test a shared access signature (SAS). Learn more about Shared Access Signatures.

- Select your uploaded blob file and move to the Generate SAS tab.
- In the Permissions drop-down, ensure the partner has only Read permissions.
- Verify the Start and expiry date/time is for the next 24 hours.
- Select Generate SAS token and URL.
- Copy the Blob SAS URL to a new browser tab.
- Verify you can access the file. If you have uploaded an image file it will display in the browser. Other file types will be downloaded.


![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/2ukcp8gerv0nusem8ict.png)

C. **CONFIGURE STORAGE ACCESS TIERS AND CONTENT REPLICATION.**

1. To save on costs, after 30 days, move blobs from the hot tier to the cool tier. Learn more how manage the Azure Blob storage lifecycle.

-  Return to the storage account.
-  In the Overview section, notice the Default access tier is set to Hot.
-  In the Data management section, select the Lifecycle management blade.
-  Select Add rule.
-  Set the Rule name to move-to-cool.
-  Set the Rule scope to Apply rule to all blobs in the storage account.
-  Select Next.
-  Ensure Last modified is selected.
-  Set More than (days ago) to 30.
-  In the Then drop-down select Move to cool storage.
-  As you have time, review other lifecycle options in the drop-down.
-  Add the rule.


![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/2v5vec2hctz61h8ipwy4.png)

2. The public website files need to be backed up to another storage account.[Learn more about object replication.

-  In your storage account, create a new container called backup. Use the default values. Refer back to Lab 02a if you need detailed instructions.


![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/tgw340litbokp5pgojck.png)

-  Navigate to your publicwebsite storage account. This storage account was created in the previous exercise.

   -  In the Data management section, select the Object replication blade.
   -  Select Create replication rules.
   -  Set the Destination storage account to the private storage account.
   -  Set the Source container to public and the Destination container to 
       backup.
   -  Create the replication rule.
   -  Optionally, as you have time, upload a file to the public container. 
   -  Return to the private storage account and refresh the backup 
      container. Within a few minutes your public website file will 
      appear in the backup folder.


![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/vw2t8bzk3villbz45zup.png)