Microsoft.Graph.Beta.DirectoryObjects
{{ Fill in the Description }}
Microsoft.Graph.Beta.DirectoryObjects
| Confirm-MgBetaDirectoryObjectMemberGroup |
Check for membership in a specified list of group IDs, and return from that list those groups (identified by IDs) of which the specified user, group, service principal, organizational contact, device, or directory object is a member. This function is transitive. You can check up to a maximum of 20 groups per request. This function supports all groups provisioned in Microsoft Entra ID. Because Microsoft 365 groups cannot contain other groups, membership in a Microsoft 365 group is always direct. Note To view the v1.0 release of this cmdlet, view Confirm-MgDirectoryObjectMemberGroup |
| Confirm-MgBetaDirectoryObjectMemberObject |
Invoke action checkMemberObjects Note To view the v1.0 release of this cmdlet, view Confirm-MgDirectoryObjectMemberObject |
| Get-MgBetaDirectoryObject |
Retrieve the properties and relationships of a directoryObject object. Note To view the v1.0 release of this cmdlet, view Get-MgDirectoryObject |
| Get-MgBetaDirectoryObjectById |
Return the directory objects specified in a list of IDs. Some common uses for this function are to: Note To view the v1.0 release of this cmdlet, view Get-MgDirectoryObjectById |
| Get-MgBetaDirectoryObjectCount |
Get the number of the resource Note To view the v1.0 release of this cmdlet, view Get-MgDirectoryObjectCount |
| Get-MgBetaDirectoryObjectDelta |
Invoke function delta Note To view the v1.0 release of this cmdlet, view Get-MgDirectoryObjectDelta |
| Get-MgBetaDirectoryObjectMemberGroup |
Return all the group IDs for the groups that the specified user, group, service principal, organizational contact, device, or directory object is a member of. This function is transitive. This API returns up to 11,000 group IDs. If more than 11,000 results are available, it returns a 400 Bad Request error with the Directory_ResultSizeLimitExceeded error code. As a workaround, use the List group transitive memberOf API. Note To view the v1.0 release of this cmdlet, view Get-MgDirectoryObjectMemberGroup |
| Get-MgBetaDirectoryObjectMemberObject |
Invoke action getMemberObjects Note To view the v1.0 release of this cmdlet, view Get-MgDirectoryObjectMemberObject |
| Get-MgBetaDirectoryObjectUserOwnedObject |
Retrieve a list of recently deleted application and group objects owned by the specified user. This API returns up to 1,000 deleted objects owned by the user, sorted by ID, and doesn't support pagination. |
| New-MgBetaDirectoryObject |
Add new entity to directoryObjects Note To view the v1.0 release of this cmdlet, view New-MgDirectoryObject |
| Remove-MgBetaDirectoryObject |
Delete a directory object, for example, a group, user, application, or service principal. Note To view the v1.0 release of this cmdlet, view Remove-MgDirectoryObject |
| Test-MgBetaDirectoryObjectProperty |
Validate that a Microsoft 365 group's display name or mail nickname complies with naming policies. Clients can use this API to determine whether a display name or mail nickname is valid before trying to create a Microsoft 365 group. For validating properties of an existing group, use the validateProperties function for groups. The following validations are performed for the display name and mail nickname properties: 1. Validate the prefix and suffix naming policy2. Validate the custom banned words policy3. Validate the mail nickname is unique This API returns with the first failure encountered. If one or more properties fail multiple validations, only the property with the first validation failure is returned. However, you can validate both the mail nickname and the display name and receive a collection of validation errors if you are only validating the prefix and suffix naming policy. Note To view the v1.0 release of this cmdlet, view Test-MgDirectoryObjectProperty |
| Update-MgBetaDirectoryObject |
Update entity in directoryObjects Note To view the v1.0 release of this cmdlet, view Update-MgDirectoryObject |