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/active-directory/devices/azuread-join-sso.md
+6-1Lines changed: 6 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,12 +21,17 @@ It is probably not a surprise that an Azure Active Directory (Azure AD) joined d
21
21
22
22
This article explains how this works.
23
23
24
+
## Prerequisites
25
+
26
+
If Azure AD joined machines are not connected to your organization's network, a VPN or other network infrastructure is required. On-premises SSO requires line-of-sight communication with your on-premises AD DS domain controllers.
27
+
24
28
## How it works
25
29
26
30
Because you need to remember just one single user name and password, SSO simplifies access to your resources and improves the security of your environment. With an Azure AD joined device, your users already have an SSO experience to the cloud apps in your environment. If your environment has an Azure AD and an on-premises AD, you probably want to expand the scope of your SSO experience to your on-premises Line Of Business (LOB) apps, file shares, and printers.
27
31
28
32
Azure AD joined devices have no knowledge about your on-premises AD environment because they aren't joined to it. However, you can provide additional information about your on-premises AD to these devices with Azure AD Connect.
29
-
An environment that has both, an Azure AD and an on-premises AD, is also known has hybrid environment. If you have a hybrid environment, it is likely that you already have Azure AD Connect deployed to synchronize your on-premises identity information to the cloud. As part of the synchronization process, Azure AD Connect synchronizes on-premises domain information to Azure AD. When a user signs in to an Azure AD joined device in a hybrid environment:
33
+
34
+
An environment that has both, an Azure AD and an on-premises AD, is also known has hybrid environment. If you have a hybrid environment, it is likely that you already have Azure AD Connect deployed to synchronize your on-premises identity information to the cloud. As part of the synchronization process, Azure AD Connect synchronizes on-premises user information to Azure AD. When a user signs in to an Azure AD joined device in a hybrid environment:
30
35
31
36
1. Azure AD sends the name of the on-premises domain the user is a member of back to the device.
32
37
1. The local security authority (LSA) service enables Kerberos authentication on the device.
Copy file name to clipboardExpand all lines: articles/backup/backup-azure-backup-server-vmware.md
+41-26Lines changed: 41 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ This article explains how to:
18
18
19
19
## Before you start
20
20
21
-
- Verify that you're running a version of vCenter/ESXi that's supported for backup - versions 6.5, 6.0, and 5.5.
21
+
- Verify that you're running a version of vCenter/ESXi that's supported for backup. Refer to the support matrix [here](https://docs.microsoft.com/azure/backup/backup-mabs-protection-matrix).
22
22
- Make sure you've set up Azure Backup Server. If you haven't, [do that](backup-azure-microsoft-azure-backup.md) before you start. You should be running Azure Backup Server with the latest updates.
23
23
24
24
## Create a secure connection to the vCenter Server
@@ -124,26 +124,41 @@ The Azure Backup Server needs a user account with permissions to access v-Center
|| Virtual Machine Contributor | Source VM that got backed up |
39
39
|| Storage Account Contributor | Storage account resource where disks are going to be restored |
40
-
| Restore managed disks from VM backup | Backup Operator | Recovery vault resource|
40
+
| Restore managed disks from VM backup | Backup Operator | Recovery Services vault|
41
41
|| Virtual Machine Contributor | Source VM that got backed up |
42
42
|| Storage Account Contributor | Temporary Storage account selected as part of restore to hold data from vault before converting them to managed disks |
43
43
|| Contributor | Resource group to which managed disk(s) will be restored |
44
-
| Restore individual files from VM backup | Backup Operator | Recovery vault resource|
44
+
| Restore individual files from VM backup | Backup Operator | Recovery Services vault|
45
45
|| Virtual Machine Contributor | Source VM that got backed up |
46
-
| Create backup policy for Azure VM backup | Backup Contributor | Recovery vault resource|
47
-
| Modify backup policy of Azure VM backup | Backup Contributor | Recovery vault resource|
48
-
| Delete backup policy of Azure VM backup | Backup Contributor | Recovery vault resource|
49
-
| Stop backup (with retain data or delete data) on VM backup | Backup Contributor | Recovery vault resource|
50
-
| Register on-premises Windows Server/client/SCDPM or Azure Backup Server | Backup Operator | Recovery vault resource|
51
-
| Delete registered on-premises Windows Server/client/SCDPM or Azure Backup Server | Backup Contributor | Recovery vault resource|
46
+
| Create backup policy for Azure VM backup | Backup Contributor | Recovery Services vault|
47
+
| Modify backup policy of Azure VM backup | Backup Contributor | Recovery Services vault|
48
+
| Delete backup policy of Azure VM backup | Backup Contributor | Recovery Services vault|
49
+
| Stop backup (with retain data or delete data) on VM backup | Backup Contributor | Recovery Services vault|
50
+
| Register on-premises Windows Server/client/SCDPM or Azure Backup Server | Backup Operator | Recovery Services vault|
51
+
| Delete registered on-premises Windows Server/client/SCDPM or Azure Backup Server | Backup Contributor | Recovery Services vault|
52
52
53
53
> [!IMPORTANT]
54
54
> If you specify VM Contributor at a VM resource scope and click on Backup as part of VM settings, it will open 'Enable Backup' screen even though VM is already backed up as the call to verify backup status works only at subscription level. To avoid this, either go to vault and open the backup item view of the VM or specify VM Contributor role at a subscription level.
Copy file name to clipboardExpand all lines: articles/backup/backup-sql-server-database-azure-vms.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
@@ -23,7 +23,7 @@ In this article, you'll learn how to:
23
23
24
24
Before you back up a SQL Server database, check the following criteria:
25
25
26
-
1. Identify or create a [Recovery Services vault](backup-sql-server-database-azure-vms.md#create-a-recovery-services-vault) in the same region or locale as the VM hosting the SQL Server instance.
26
+
1. Identify or create a [Recovery Services vault](backup-sql-server-database-azure-vms.md#create-a-recovery-services-vault) in the same region and subscription as the VM hosting the SQL Server instance.
27
27
2. Verify that the VM has [network connectivity](backup-sql-server-database-azure-vms.md#establish-network-connectivity).
28
28
3. Make sure that the SQL Server databases follow the [database naming guidelines for Azure Backup](#database-naming-guidelines-for-azure-backup).
29
29
4. Check that you don't have any other backup solutions enabled for the database. Disable all other SQL Server backups before you back up the database.
0 commit comments