Announcements
We are currently using the new Vibe Power Apps feature, and we are facing an issue retrieving the dynamically logged-in user details. At the moment, we are unable to get the current user’s email or profile information within the Vibe app.
This makes it difficult to manage user roles dynamically for both developers and end users. The app is using the Microsoft 365 connector, but we are still unable to retrieve the logged-in user’s email.
Is this a known limitation or a bug from Microsoft? If so, is there any update planned to address this? Alternatively, is there any workaround available to fetch the currently logged-in user details dynamically in Vibe Power Apps?
Hi @Athish,
Primarily the Vibe app's runtime environment currently restricts or does not fully support certain user context APIs that the Microsoft 365 connector relies on for fetching user profile information -Microsoft has acknowledged this as a limitation rather than a bug!
Bit expensive workaround might be, if possible in you cases:
Please let me know if this helps.
The error message "Looks like this feature is not supported here" when opening the Vibe portal in a US region environment typically indicates that the Vibe Power Apps feature is not yet available or enabled in that specific region or environment type.
Currently, Microsoft is rolling out the Vibe experience gradually, and some regions or environment types (such as certain government, sovereign, or newly created environments) may not have full support yet. This is not necessarily a bug but a known limitation during the phased rollout.
To address this:
Verify that the environment type and region are supported for Vibe by checking the official Microsoft Power Apps documentation or release notes.
Confirm that the user has the necessary licenses and permissions to access the Vibe feature.
Check if the environment is a production or trial environment, as some preview features may be limited to specific environment types.
If the environment is newly created, sometimes waiting a few hours or days after creation helps as feature availability propagates.
Consider opening a support ticket with Microsoft if the environment should support Vibe but still shows this error.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Jump in, show your community spirit, and win prizes!
Expanding mentorship, skilling, and AI innovation
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Valantis 424
WarrenBelz 355 Most Valuable Professional
11manish 290
