Chime usage for external partners

Based on the information available, there are a few potential reasons why older users with the old company name might be experiencing issues with Amazon Chime:

1. Account Management: If the partner company uses an Enterprise account for Amazon Chime, there might have been changes in user management or permissions. Enterprise account administrators can suspend user access, which would prevent users from signing in. It's possible that during the company name change, some user accounts were not properly updated or transferred.

2. Authentication Method: For Enterprise accounts, users typically sign in with Active Directory or Okta credentials. If there were changes to the authentication system during the company name change, it could affect older user accounts.

3. Invitation and Access: If the older users were not properly re-invited or their access was not updated after the company name change, it could result in access issues.

4. Account Type Changes: If the partner switched from a Team account to an Enterprise account (or vice versa) during the name change, it could affect how user permissions are managed.

To resolve this issue, the partner company's Amazon Chime administrator should:

1. Check the status of the affected user accounts in the Amazon Chime console.
2. Verify if the users' permissions are still active and correctly set.
3. Ensure that the authentication method for these users is still valid and properly linked to their accounts.
4. If necessary, re-invite the affected users or update their account information to reflect the new company name.

If the issue persists, it would be advisable for the partner to contact Amazon Chime support for further assistance, as they would have more detailed information about the account and any recent changes that might have affected user access.

Sources
Managing user permissions and access - Amazon Chime
Amazon Chime - FAQs