Viva Engage - Import users with CSV fails with Failure Reason: Unclassified

Anonymous
2025-02-02T23:39:32+00:00

What reason are import failures on Viva Engage occuring with Failure Reason: "Unclassified" and how can this be resoved?

Microsoft 365 and Office | Microsoft Viva | Viva Engage

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2025-02-05T10:12:34+00:00

So far no solution, however the case is being escalated to MS Engineering for more effort.

Until solved, there is a workaround by using Entra to upload users via the bulk operations option shown below:

Was this answer helpful?

5 people found this answer helpful.
0 comments

22 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2025-02-26T14:01:33+00:00

    Just ran this for updating group in Viva via M365 underlying group. It's quick and dirty - feel free to adjust per your needs

    Install Exchange Online module in case not installed

    Install-Module -Name ExchangeOnlineManagement

    Connect to Exchange Online

    Connect-ExchangeOnline

    Specify the group name and CSV file path

    $GroupName = "viva_community_email_******@yourdomain.com"

    $CSVFilePath = ".\File_To_Import.csv"

    Note that the file should have a column with a heading of UserPrincipalName

    This column should contain email addresses of everyone you want to import

    Import the CSV file into a variable

    $MembersToImport = Import-Csv $CSVFilePath

    Get the group object

    $Group = Get-UnifiedGroup $GroupName

    $Members = Get-UnifiedGroupLinks -Identity $GroupName -LinkType Member

    Write-Warning "Group Members: " ${Members}

    Remove existing members if you want to replace with only what's in the CSV

    Remove-UnifiedGroupLinks -Identity $Group -LinkType Members -Links $Members

    Add new members from the CSV file

    foreach ($member in $MembersToImport) { 

    Add-UnifiedGroupLinks -Identity $Group -LinkType Member -Links $member.UserPrincipalName 

Write-Warning $member.UserPrincipalName

    }

    Write-Host "Members updated successfully."

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2025-02-26T13:41:13+00:00

    I just tested a workaround solution which should at least let me move forward. You can add members to the underlying Viva Engage M365 groups (tested manually - added users show up in Viva community). So I just have to PowerShell script the group update from CSV. I have a script to do this. Once I successfully run it, I'll post the script here in case it helps anyone else.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2025-02-26T11:52:55+00:00

    I am getting the same issues and really need this resolving as soon as possible please.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2025-02-24T15:29:51+00:00

    FYI - my MS support team has informed me there is an issue on their end. Engineers have discovered a bug and made a fix. I am told they're prepared to begin deploying on 2/25 after making final tests over the weekend.

    Hi,

    I have the same issue and have done a bulk from Azur as well with no luck.

    Me and a colleague gets "unclassified" error.

    Checked the data an no special characters or such.

    Would be great if this could be fixed asap! since this is a community intended to have many users.

    I need to add +1000 and that will not be done manually.

    Thanks!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments