Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v5 migration guide #1619

Open
hamounir opened this issue Dec 4, 2024 · 6 comments
Open

v5 migration guide #1619

hamounir opened this issue Dec 4, 2024 · 6 comments
Assignees

Comments

@hamounir
Copy link

hamounir commented Dec 4, 2024

As reference Microsoft ticket number: RE: [EXTERNAL] RE: VIP - Teams cannot access Co... - TrackingID#2411290050002538

we need remote session support to migrate our company communicator to be v5 migration guide.
https://github.com/OfficeDev/microsoft-teams-apps-company-communicator/wiki/v5-migration-guide

Regards,
Hamid
call me on +201123202342
email to me: [email protected]

@v-jaygupta
Copy link
Collaborator

Hi @hamounir,
Thanks for reaching out to us!
Please let us know which is the version of the Company Communicator app which is currently deployed in your tenan?
If the deployed version is v5.x, please follow the v5 migration guide to upgrade to the latest version of CC app i.e. v5.5.2.

@v-jaygupta
Copy link
Collaborator

@hamounir ,
Could you please let us know if you are still facing this issue and require assistance and we will be happy to discuss. If no further action is needed at the moment, can we close this issue?
You may also always open a new issue or respond here if something does come back up.

@hamounir
Copy link
Author

hamounir commented Dec 13, 2024 via email

@v-jaygupta
Copy link
Collaborator

@hamounir ,
Please share the details requested earlier in the previous comments

@v-jaygupta
Copy link
Collaborator

@hamounir,

Thank you for submitting this issue, as we work to ensure consistent responses with items logged in our issues list, we are working to address these items that did not get responses.
Please let us know if you are still facing this issue and require assistance and we will be happy to discuss. If no further action is needed at the moment and no response is received, we will close out the issue by tomorrow EOD.
You may also always open a new issue over GitHub if something does come back up.

@hamounir
Copy link
Author

hamounir commented Dec 18, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants