To allow Microsoft Power Apps login using another organization's email (external user)

 

To configure Azure AD B2B (Business-to-Business) collaboration or Guest Access in Microsoft Entra ID (formerly Azure AD). Here’s how you can do it:

1. Add External Users to Your Tenant

1. Go to Azure Portal (https://portal.azure.com).
2. Navigate to Microsoft Entra ID (formerly Azure Active Directory).
3. Click on Users > External Identities > New guest user.
4. Enter the external user’s email (from the other organization).
5. Choose Invite user and send the invitation.

2. Assign Power Apps Access to External Users

1. Go to Power Platform Admin Center (https://admin.powerplatform.microsoft.com).
2. Select Environments and choose the relevant environment.
3. Under Users + permissions, select Users.
4. Click Add user, enter the guest user's email, and assign necessary roles.

3. Allow External Users to Sign In

• Ensure Guest user access settings allow external users to authenticate.
• In Microsoft Entra ID > External Identities > Cross-tenant access settings, configure the organization’s access policies.

4. Share the Power Apps App

1. Open Power Apps (https://make.powerapps.com).
2. Select the app you want to share.
3. Click Share, enter the external user's email, and assign permissions.

5. Verify Sign-in & Permissions

• The external user should accept the email invitation.
• They must sign in using https://make.powerapps.com with their organization’s email.
• If they encounter issues, ensure Conditional Access policies aren’t blocking external logins.

Backups fail with error V-79-1000-10660 - 03E829A4 - An error was encountered writing to the on-disk catalogs.

 

Problem

 Backup operations performed with Backup Exec fail with error V-79-1000-10660 - 03E829A4 - An error was encountered writing to the on-disk catalogs.

Error Message

 V-79-1000-10660 - 03E829A4 - An error was encountered writing to the on-disk catalogs.

Cause

The failure occurs because Backup Exec is experiencing one of the following conditions:

• The drive the Catalogs folder is hosted on does not have enough free space to store the Backup Exec temporary catalog files.
• The Catalog path in Backup Exec points to an invalid location. The current location of the Backup Exec catalog files can be viewed by going to the Tools | Options | Catalog menu in Backup Exec.
• The Backup Exec Service Account (BESA) does not have adequate permissions to write to the Catalogs folder. This commonly occurs when a security change affected a top level parent folder and replicated down to the Catalogs folder.
• Anti-virus software was running at the time of the backup

Any of these issues result in a condition which prevents the BE Service Account from writing the temporary catalog files.

 

Solution

 To resolve the issue, perform one of the following:

1. Move the Backup Exec catalog files to a drive that has more free space. 
2. Verify the catalog location exists in the Windows directory. If it does not exist, change the catalog directory in Backup Exec.
   1. Open Backup Exec
   2. Go to Tools -  Options - Catalog
   3. Modify the catalog path
3. Free up space on the drive where the catalog files are currently located.
4. Modify the security restrictions on the Catalogs folder, giving Full Control to the Backup Exec Service Account.
5. Setup an exclusion in any anti-virus software that is running on the Media Server (the server Backup Exec is installed on) so that Backup Exec directories and files will not be scanned.

ADSIEdit Error: There Is No Editor Registered To Handle This Attribute Type

 

Problem

If you attempt to edit the authOrig attribute of a mail enabled group using ADSIedit you will get the following error.

Solution:

Use PowerShell

You can (if you have no access to Exchange Management tools) simply use PowerShell, the syntax is as follows.

Set-ADGroup -Identity "The-Group" -Server The-Domain-Controller -Add @{authOrig=@('The User or Group to Grand access to')}

e.g.

Set-ADGroup -Identity "CN=DG-Test-Disty-Group,CN=Users,DC=pnl,DC=com" -Server PNL-MGMT.pnl.com -Add @{authOrig=@('CN=Pete Long,CN=Users,DC=pnl,DC=com')}

Then to verify, you can go back to ADSIedit and check.