i'm creating EMM-managed enterprise. This is the recommended method (no signup page nor google account required)
https://developers.google.com/android/management/create-enterprise#emm-managed_enterprises
but, with this enterprise, end user have no IT admin account to connect to managed google play on https://play.google.com/work
what is the correct way to approve applications with this type of enterprises?
EMM Managed enterprise is no longer the recommended method to create an enterprise, Instead, we suggest starting a Customer-managed enterprises.
Additionally, with Android Management API any application added under the application policy behaves based on the configured installType. The play store mode policy determines the behavior of the apps on the device play store.
You will still need to follow all of the policy distribution steps mentioned in this documentation.
Related
With Android 12 and Android Management API i can use built-in Android Device Policy app to deploy policies on different devices.
No problem to enroll a new device or to push policies on it.
But i need to use DevicePolicyManager#addOverrideApn method to set custom APN on device. This method needs device owner permission in order to use it.
How can i use it without build a custom DPC?
Custom DPC was not encouraged by Google as mentioed here: https://developers.google.com/android/work/play/emm-api/register
Can i use it via delegated scope application policy?
Thanks in advance
Unfortunately, adding override APN is not yet supported in the Android Management API. Our Engineering team has created a related feature request for future review. Please note that the ticket is in our backlog for future consideration and has not been picked up for work. Therefore, we don't have any immediate plans or timelines associated with the request.
If you want to stay up to date with the latest updates for Android enterprise, we suggest that you join the Android Management API mailing list to receive monthly updates and service advisories directly to your inbox.
I have a Teams application (Tab). I am an ISV provider, and provide a multi-tenant application that is installed by customers via Teams App Store in their organizations.
How do I save settings for my application organization-wide for the customers? For example, CustomerA has installed the app and then CustomerB. I want some storage that would be unique for CustomerA and CustomerB and the app, and located in customer's environment. The settings I want to save are not per-user, but per-organization (tenant).
Somewhat similar to "App Data" folder you have in Windows Desktop for example.
Does such a storage exist? Does API for this storage exist?
A tab app is a simply a web application that you render inside of Teams. As a result, what the app does, and where and how it does it, is totally up to you. This includes any data storage you choose to have behind the scenes. For example, your tab could be built in PHP and use MySQL, or built in ASP.Net and use SQL Azure or CosmosDB. It's totally up to you, but you need to implement it yourself, as an ISV.
The important piece to differentiate clients, however, is being aware of the TenantId for each user, so you can look up which client's settings you need from the database. The most simple way to do this is simply the tid property on the Teams tab context. You can read more about that here. Unfortunately, because it's just accessed via Javascript, it's not entirely secure - for a more secure mechanism, you should be creating an Azure Application, and generating jwt tokens that you can authenticate against in your backend. It's a much more complex topic, but hopefully this answer at least gives the background you need. For more info on the security aspects (validating the token etc.), please see this question: How to restrict access to Azure Function to only allow requests from a custom Microsoft Teams App?.
I am investigating why I cannot set up a hook to integrate Teams and Azure DevOps. I am running two versions in different environments for comparison- but I am trying to hook the two together in the same environment.
First environment, version 1.3.00: This has the app built-in for Azure DevOps to hook and connect with Teams
Second environment, version 1.2.00: This version has no 'manage apps' button, and does not have anything referencing Azure DevOps or allowing to make any connection between Azure and Teams. This is the environment I am trying to make the connection in.
Any thoughts on this? Does 1.2.00 version not offer the hook between Teams and Azure DevOps? We do not have O365 accounts for this environment.
To access the Manage apps page, you must be a global admin or Teams service admin. You may check your permission. Also, add microsoft-teams tag for you case may help you get more assistance.
https://learn.microsoft.com/en-us/microsoftteams/manage-apps
I am integrating my SAAS application to Microsoft Teams. Right now integrated as Tab in teams. I am using my own API endpoint to authenticate and authorize the user. I have got some specific information about the user I am getting from API. How can I store it in Team context? Right now I used local storage in the web app. In Teams web app it seems working but I don't think it is working in Desktop app. Is there some API available in teams which helps to maintain the user state with Tabs? similar to userstate in Bots? Please help.
I would think local storage would be troublesome across devices anyway, perhaps consider server-side storage instead.
I administrate users in Cloud Identity Free Edition now.
They can't use Google Drive, Colaboratory, Spread Sheet, and so on after they started being controlled in Cloud Identity.
What should I do to allow them to use those services again with controlling them?
Should I switch Free Edition to Premium Edition or GSuite?
Correction to my answer earlier to this topic.
Google Drive is actually present in Cloud Identity Free and Premium Edition.
It is just limited to 15GB per User. Just have a look at the Cloud Identity Core Services
You have to activate it in the Admin Console (https://admin.google.com), and after that it is available for all users in the domain, Organizational Unit or group, that you have chosen to activate it for.
If you need additional configuration options to control the access to drive and the sharing possibilities in your domain, you should however switch to a G Suite Licence