Skip to content
This repository has been archived by the owner on Nov 16, 2023. It is now read-only.

Commit

Permalink
Merge pull request #28 from microsoft/may-2019-update
Browse files Browse the repository at this point in the history
May 2019 update
  • Loading branch information
DawnmarieDesJardins committed May 7, 2019
2 parents c8606c4 + de9ab16 commit 76bb9d4
Show file tree
Hide file tree
Showing 122 changed files with 1,378 additions and 1,350 deletions.
13 changes: 13 additions & 0 deletions .vscode/settings.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
{
"cSpell.words": [
"Greenwald",
"RBAC",
"Timeframe",
"backdoors",
"chargeback",
"datacenter",
"datacenters",
"executables",
"whitelists"
]
}
41 changes: 24 additions & 17 deletions Hands-on lab/Before the HOL - Enterprise-ready cloud.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ Before the hands-on lab setup guide
</div>

<div class="MCWHeader3">
November 2018
May 2019
</div>

Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
Expand All @@ -18,7 +18,7 @@ Microsoft may have patents, patent applications, trademarks, copyrights, or othe

The names of manufacturers, products, or URLs are provided for informational purposes only and Microsoft makes no representations and warranties, either expressed, implied, or statutory, regarding these manufacturers or the use of the products with any Microsoft technologies. The inclusion of a manufacturer or product does not imply endorsement of Microsoft of the manufacturer or product. Links may be provided to third party sites. Such sites are not under the control of Microsoft and Microsoft is not responsible for the contents of any linked site or any link contained in a linked site, or any changes or updates to such sites. Microsoft is not responsible for webcasting or any other form of transmission received from any linked site. Microsoft is providing these links to you only as a convenience, and the inclusion of any link does not imply endorsement of Microsoft of the site or the products contained therein.

© 2018 Microsoft Corporation. All rights reserved.
© 2019 Microsoft Corporation. All rights reserved.

Microsoft and the trademarks listed at <https://www.microsoft.com/en-us/legal/intellectualproperty/Trademarks/Usage/General.aspx> are trademarks of the Microsoft group of companies. All other trademarks are property of their respective owners.

Expand All @@ -27,20 +27,19 @@ Microsoft and the trademarks listed at <https://www.microsoft.com/en-us/legal/in
<!-- TOC -->

- [Enterprise-ready cloud before the hands-on lab setup guide](#enterprise-ready-cloud-before-the-hands-on-lab-setup-guide)
- [Requirements](#requirements)
- [Before the hands-on lab](#before-the-hands-on-lab)
- [Task 1: Validate global admin access to Azure AD tenant](#task-1-validate-global-admin-access-to-azure-ad-tenant)
- [Task 2: Setup a development environment](#task-2-setup-a-development-environment)
- [Requirements](#requirements)
- [Before the hands-on lab](#before-the-hands-on-lab)
- [Task 1: Validate global admin access to Azure AD tenant](#task-1-validate-global-admin-access-to-azure-ad-tenant)

<!-- /TOC -->

# Enterprise-ready cloud before the hands-on lab setup guide

## Requirements

- Local machine or a virtual machine configured with:
- Visual Studio 2015 or 2017 Community Edition or VS Code.
- Full global admin access to the Azure AD tenant associated with your Azure subscription.
- Full global admin access to the Azure AD tenant associated with your Azure subscription.

> **Note**: In this lab, [Azure Cloud Shell](https://docs.microsoft.com/azure/cloud-shell/overview) is used for executing commands using the Azure CLI and Azure PowerShell. Both the Azure CLI and Azure PowerShell can be installed locally if needed.
## Before the hands-on lab

Expand All @@ -50,20 +49,28 @@ To complete this lab, you must have full global admin access to the Azure AD ten

### Task 1: Validate global admin access to Azure AD tenant

1. Login to <http://portal.azure.com>, click on **All Services**, and type in **Azure Active Directory**.
To validate that you have Global Administrator access to your Azure AD tenant, we will elevate access for a Global Administrator to allow for the management of Azure resources.

1. Sign in to the [Azure portal](https://portal.azure.com/) or the [Azure Active Directory admin center](https://aad.portal.azure.com/) as a Global Administrator.

2. In the navigation list, click **Azure Active Directory** and then click **Properties**.

![Azure Active Directory Properties blade in the Azure portal.](images/Setup/image1.png "Properties blade")

3. Under *Access management for Azure resources*, set the toggle to **Yes**.

2. Open the Azure Active Directory tenant. Click Users -\> New User.
![Azure Active Directory Properties blade in the Azure portal with the Access management for Azure resources set to Yes.](images/Setup/image2.png "Properties blade - Access management for Azure resources")

3. Create a new user called testuser/test1. Use the tenant name on the header for the domain name of the email.
> **Note**: When you set the toggle to Yes, you are assigned the User Access Administrator role in Azure RBAC at the root scope (/). This grants you permission to assign roles in all Azure subscriptions and management groups associated with this Azure AD directory. This toggle is only available to users who are assigned the Global Administrator role in Azure AD.
![Create user Azure portal blade with user name and email domain name highlighted.](images/Setup/image3.png "Create User blade")
4. Click **Save** to save your setting.

>**Note:** If you can create the user, you will enough permissions in Azure AD to complete the lab. If you cannot, you will need more permissions before proceeding.
![Azure Active Directory Properties blade in the Azure portal with the Save button highlighted.](images/Setup/image4.png "Properties blade - Save button")

### Task 2: Setup a development environment
> **Note**: This setting is not a global property and applies only to the currently signed in user. You can't elevate access for all members of the Global Administrator role.
If you do not have a machine set up with Visual Studio, complete this task and use this VM to complete the remainder of the Lab.
5. Login to <http://portal.azure.com>, click on **All Services**, and type in **Azure Active Directory**.

1. Create a DS2\_V2 Azure Virtual Machine using the Visual Studio Community 2017 image from the Azure Marketplace.
6. Sign out and sign back in to refresh your access.

You should follow all steps provided *before* performing the Hands-on lab.

0 comments on commit 76bb9d4

Please sign in to comment.