Chat now with support
Chat mit Support

Enterprise Reporter 3.5 - Configuration Manager User Guide

Product Overview Configuring the Configuration Manager
Starting the Configuration Manager Finding answers and getting help Overview of Enterprise Reporter Communications and Credentials Required Using the Credential Manager Setting Up Your First Collection Computers (Nodes) Modifying Your Deployment Configuring Global Settings Customizing the Configuration Manager View
Understanding Discoveries Creating Discoveries
Step 1. Create the Discovery (Name) Step 2. Choose what to include in your discovery (Scopes) Step 2a. Choose scopes for your on-premises discoveries
Choosing your Active Directory Scopes Choosing your Computer Scopes Choosing Your Exchange Scopes Choosing Your File Storage Analysis Scopes Choosing Your Microsoft SQL Scopes Choosing Your NTFS Scopes Choosing Your Registry Scopes
Step 2b: Choose scopes for your cloud discoveries Step 3. Schedule your Discovery Step 4: Review the summary
Managing Discoveries Troubleshooting Issues with Enterprise Reporter Appendix: PowerShell cmdlets Appendix: Encryption Key Manager Appendix: Log Viewer

Choosing Your Azure Active Directory Scopes

Azure Active Directory discoveries, by default, target the tenant that you specified with the credentials on the Name page in Step 1. Create the Discovery (Name) .

Information about your contacts, users, groups, group members, roles, and application service principals is collected based on the discovery options.

Azure AD Discovery: Decide what to collect from the tenant in the discovery

You can collect a variety of information from the Azure tenant in your discovery. Basic information from the tenant (the tenant name and full LDAP path), subscriptions, licenses, and service plans is always collected.

The following table outlines the additional information that can be collected. Collecting additional information impacts discovery performance. Options with a high performance cost will slow discovery performance more than options with a medium or low performance cost.

 
Table 33. Azure Active Directory Discovery: Optionally collect information for the following objects
Option
Notes
Performance Cost

Users

Collects basic information for all user accounts.

Medium

•
Additional attributes from Office 365

If collecting users, you can enable this option to collect additional attributes such as AboutMe, Birthday, HireDate, Interests, MySite, PastProjects, PreferredName, Responsibilities, Schools, and Skills.

High

•
Multi-Factor Authentication attributes

If collecting users, you can enable this option to collect Multi-Factor Authentication information.

NOTE: Microsoft Azure Active Directory Module for Windows PowerShell is required on the node machines to collect multi-factor authentication attributes for Azure Users.

Medium

•
Users flagged as risky

If collecting users, you can enable this option to collect users flagged for risk.

Medium

Groups

Collects basic information for all groups including direct members.

Medium

•
Additional attributes from Office 365

If collecting groups, you can enable this option to collect additional attributes such as AutoSubscribeNewMembers, and IsSubscribedByMail.

High

Contacts

Collects basic information for all contacts.

Low

Devices

Collects basic information for all devices and their users.

Medium

Roles

Collects basic information for all standard roles including role direct members.

Low

Applications and Service Principals

Collects information for all applications and service principals including the user and group assignments.

High

 
* 
NOTE: Microsoft 365 discoveries support both Multi-Factor Authentication enabled and disabled credentials. However, using Multi-Factor Authentication enabled credentials on Microsoft 365 discoveries can result in an incomplete collection that omits one or more objects and attributes. For more information, see Multi-Factor Authentication Discovery Credential Limitations .

Choosing Your Azure Resource Scopes

Azure Resource discoveries, by default, target the tenant that you specified with the credentials on the Name page in Step 1. Create the Discovery (Name) . Information about your resources is collected based on the discovery options.

See also:

•
Azure Resource Discovery: Include Scopes
•
Azure Resource Discovery: Optionally refine your scope list with exclusions
•
Azure Resource Discovery: Decide what to collect from the subscriptions in the discovery

 

Azure Resource Discovery: Include Scopes

By default, the discovery collects information from the subscriptions you specify. You can change the scope to collect all subscriptions. For full information on using the browser to add scopes, see Step 2b: Choose scopes for your cloud discoveries .

To specify whether to collect all subscriptions or only specific subscriptions
•
Select Collect only selected subscriptions to explicitly include individual subscriptions in the scope.
* 
NOTE: This option is recommended when the majority of the subscriptions on the target tenant do not need to be collected. For more information, see To explicitly include objects in your Azure Resource scope .
- OR-
Select Collect all subscriptions with the option to exclude selected subscriptions to collect all available information from most or all of the subscriptions on the target tenant.
* 
NOTE: This option is recommended when the majority of the subscriptions on the target tenant must be collected. For more information, see Azure Resource Discovery: Optionally refine your scope list with exclusions .
To explicitly include objects in your Azure Resource scope
1
Click Add to populate the subscription list with all subscriptions for all credentials provided on the Name page.
2
In the treeview, locate the object to include and select it.
To select multiple objects, press Ctrl during selection.
3
Click Include to add to your selected scopes list.
4
Click OK.
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen