You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/devtest/offer/concepts-security-governance-devtest.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,21 +24,21 @@ Important tools within Azure Dev/Test Subscriptions help you create secure acces
24
24
25
25
When enabling and setting up your Azure Dev/Test Subscriptions, Azure deploys a default resource hierarchy to manage identities and access to resources in a single Azure Active Directory domain. The resource hierarchy allows your organization to set up strong security perimeters for your resources and users.
26
26
27
-

27
+

28
28
29
29
Your resources, resource groups, subscriptions, management groups, and tenant collectively make up your resource hierarchy. Updating and changing these settings in Azure custom roles or Azure policy assignments can effect every resource in your resource hierarchy. It's important to protect the resource hierarchy from changes that could negatively impact all resources.
30
30
31
31
[Azure Management Groups](../../governance/management-groups/overview.md) are an important aspect of governing access and protecting your resources in a single tenant. Azure Management Groups allows you to set quotas, Azure policies, and security to different types of subscriptions. These groups are a vital component of developing security for your organization's dev/test subscriptions.
32
32
33
-

33
+

34
34
35
35
As you can see above, using management groups changes the default hierarchy and adds a level for the management groups. This behavior can potentially create unforeseen circumstances and holes in security if you don’t follow the [appropriate process to protect your resource hierarchy](../../governance/management-groups/how-to/protect-resource-hierarchy.md)
36
36
37
37
## Why are Azure Management Groups useful?
38
38
39
39
When developing security policies for your organization's dev/test subscriptions, you may choose to have multiple dev/test subscriptions per organizational unit or line of business. You can see a visual of that management grouping below.
40
40
41
-

41
+

42
42
43
43
You may also choose to have one dev/test subscription for all of your different units.
44
44
@@ -51,7 +51,7 @@ This security barrier has two components:
51
51
52
52
## Using Azure Active Directory Tenants
53
53
54
-
[A tenant](../../active-directory/develop/quickstart-create-new-tenant.md)is a dedicated instance of Azure AD that an organization or app developer receives when the organization or app developer creates a relationship with Microsoft like signing up for Azure, Microsoft Intune, or Microsoft 365.
54
+
[A tenant](../../active-directory/develop/quickstart-create-new-tenant.md)is a dedicated instance of Azure AD that an organization or app developer receives when the organization or app developer creates a relationship with Microsoft like signing up for Azure, Microsoft Intune, or Microsoft 365.
55
55
56
56
Each Azure AD tenant is separate from other Azure AD tenants. Each Azure AD tenant has its own representation of work and school identities, consumer identities (if it's an Azure AD B2C tenant), and app registrations. An app registration inside your tenant can allow authentications from accounts only within your tenant or all tenants.
Copy file name to clipboardExpand all lines: articles/devtest/offer/how-to-add-users-directory.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,7 +35,7 @@ Once you’ve determined you need to add a user, you must understand where you'r
35
35
36
36
If the project and tasks you're working on need to be monitored by IT to enable security protocols, you'll need that user to have an Admin role within the Management group to have full access and permissions within the subscription.
37
37
38
-

38
+

39
39
40
40
However, if you're collaborating with another developer or a colleague, they may only need access at the resource or resource group level.
Copy file name to clipboardExpand all lines: articles/devtest/offer/how-to-change-directory-tenants-visual-studio-azure.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,13 +19,13 @@ You may need to change the Active Directory you’re working in or [transfer you
19
19
20
20
When activating your subscription, your identity is created based on the email you use. That identity is either associated with your organization’s Active Directory tenant or a new directory tenant is created for that identity. You can see the identity you’re using in the upper right-hand side of your Azure portal.
21
21
22
-

22
+

23
23
24
24
From here, you can either switch identities or switch directories. You may need to change your identity to access certain directories.
25
25
26
26
If the identity you’re logged in as is associated with multiple directories, switch by selecting “Switch directory.” You'll see the directories your current identity is associated with.
27
27
28
-

28
+

29
29
30
30
Your experience within the portal is highly dependent on the directory associated with the identity you used. To change directory tenants, an Admin will have to add your identity as a user within the target directory.
31
31
@@ -37,17 +37,17 @@ If you set up your credit subscription using a personal account, your identity a
37
37
38
38
Below is a simple diagram that shows the basic steps taken when you change or transfer your subscription.
39
39
40
-

40
+

41
41
42
42
## Identity and Access Management
43
43
44
44
Where and how you have access dictates what you see based on your logged in credentials. This access can be given at different levels within the organization’s hierarchy. You can be given access at the directory level, subscription level or within resource groups.
45
45
46
-

46
+

47
47
48
48
You can see and manage your access levels within Access Control. You can also manage others' access to the subscription depending on your access levels.
49
49
50
-

50
+

51
51
52
52
## How to Change your Azure Directory Tenant
53
53
@@ -61,16 +61,16 @@ Once you’ve been added and given proper permissions, you can switch directorie
61
61
1. Sign in and select the subscription you want to use from the [Subscriptions page in Azure portal](https://portal.azure.com/#blade/Microsoft_Azure_Billing/SubscriptionsBlade)
62
62
2. Select “Change Directory”
63
63
64
-

64
+

65
65
3. A box will surface to choose the new directory
66
66
4. Select “Change”
67
67
68
68
> [!NOTE]
69
69
> If you don’t have access to the target directory it will not show. After the directory is changed for the subscription, you'll receive a success message.
70
70
71
-

71
+

72
72
5. Select “Switch Directories” on the subscription page to access the new directory
73
73
74
-

74
+

75
75
76
76
You can also access a target directory and change your tenancy by going to the target directory and adding an Admin. Follow [these instructions](/visualstudio/subscriptions/cloud-admin.md) on how to add an Admin to your subscription. Once that’s done, the Admin has access to both directories and can change the tenant directory for you.
Copy file name to clipboardExpand all lines: articles/devtest/offer/how-to-manage-monitor-devtest.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ Azure’s cloud environment gives you flexibility in managing cost and workloads
17
17
18
18
Services within the subscription and resource group levels is zero cost – only the resources themselves have cost to them.
19
19
20
-

20
+

21
21
22
22
When managing from an operational expense perspective, you only pay for what you use. There are several tools with Azure dev/test subscriptions that help you manage cost during deployment.
Copy file name to clipboardExpand all lines: articles/devtest/offer/how-to-sign-into-azure-with-github.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,15 +37,15 @@ Support for GitHub authentication makes it easier to experiment with Azure servi
37
37
38
38
To get started with the Azure Monthly Credit Subscription using your GitHub account, select “Sign in using GitHub” on any [Microsoft sign in page](https://login.microsoftonline.com)
39
39
40
-

40
+

41
41
42
-

42
+

43
43
44
44
If you haven’t activated your credits yet, go to the [Monthly Azure Credits for Visual Studio Subscribers](https://azure.microsoft.com/pricing/member-offers/credit-for-visual-studio-subscribers) page, select “Activate Your Credits” then “Sign in with GitHub” to get started.
45
45
46
-

46
+

47
47
48
-

48
+

49
49
50
50
Once you complete the sign-in process, you'll be taken to the last Azure Visual Studio organization you visited. If you’re brand new to Azure Visual Studio and Credits Subscription, you’ll land within a new organization created for you.
0 commit comments