Adding Outlook add-ins and permissions
Wonderoig if someone can answer a question for me. I'll use the process in this link as context https://help.draftable.com/hc/en-us/articles/46382047949977-Configuring-Redline-in-Email-Outlook-with-Draftable In short when adding an Outlook Addin and selecting a group to assign the add-in too and the accepting the permission requests does this: Apply the permissions to ONLY those nominated users' mailboxes; or Applies the permissions to ALL mailboxes and applies "security" by limiting the users who can see the add-in I assume it does one of the two. Any ideas?
MTO and access to on premises file system
Let me preface this by saying I'm still fairly new to 365 Admin (it's been a steep learning curve) and haven't even got my feet wet with on premises stuff as yet. Also, I think some of the admin decisions made previously by others may have been based on just repeating what was found to work the first time rather than necessarily a deep understanding of the best solution. The situation when I arrived on the scene was this (actually it was a bit more complex and messy than this, but this simplified description covers the salient points at this stage) One tenant, with two domains, call them old-domain and new-domain. Two types of user, who I will refer to operations and corporate. An on premises Active Directory system running a file server. Well to be more precise on three premises with mirroring of data and a DFS, but from the user perspective when you're one of the office locations and connect to the network the same folders are available to you. Everyone was using Azure Joined Company Laptops to do this, so their laptop logins were also their network logins. Outside of the offices people connected to the DFS using a VPN (with three gateways in different countries). Operations Users had one account, @old-domain, this was licensed for 365 and had a mailbox associated with it. It was also synched to their on premises AD account Corporate Users had two accounts, one @old-domain with no license, synched to an on premises AD account. The second was new-domain with a 365 license and mailbox. If you're scratching your head wondering why two accounts rather than assigning the new-domain email address to the same account, I can't give you a definitive answer as I've never been given one, but for whatever reason when new domains were brought into play on corporate name changes the admins gave them new mailboxes rather than simply aliasing email addresses to the same mailbox (some people had three accounts as a result). What I did note was that when a new Corporate user was added the admins gave them both of the above accounts, I was told that the unlicensed old-domain one was required for the access to the DFS. Now for reasons not worth getting into here, a decision was made to move the Corporate users to a new tenant, along with new-domain and then to link the two tenants in a multi-tenant organization. It was also decided to leverage BYOD for Corporate users, so their devices will only be Azure registered. This has been done, there was some pain thanks to the reluctance of Microsoft applications to switch to the new account locations rather than redirecting back to the old tenant, but that's been sorted. So right now Corporate users still have two accounts, but on two tenants. On the Old Tenant they have their @old-domain account, no license, no mailbox, synched to the on premises AD (as before) On the New Tenant they have their new-domain account. This is where they actually do their work, and is the only account anyone should be communicating with internally or externally. Access to the DFS is being done using the VPN with the on premises credentials associated with the old-domain account. In terms of functionality, this works perfectly well, people across the two tenants appear in each other's address lists, they can chat and share information etc. Everybody also has access to the folders they should have access to on the DFS. However there are two issues. The first, and most detrimental in terms of just getting work done is that users in one of the overseas offices have found their access to the DFS has slowed considerably, despite being in physically the same location as the data. I believe the problem is that although the data is on-premises, the VPN gateway is not, therefore data does a round trip from the server, through that gateway IP address at the ISP and back to the user. Since they are in a remote location with poor internet this slows things considerably. So the first question is, how do we take that loop out of the equation so that when they are in the office they connect more directly to the servers on site? Ideally without having to revert to needing an Azure AD joined device. The second issue is that those remaining old-domain accounts (the ones for the Corporate users who are now working on the new tenant) on the old tenant are messy, in two ways 1) From an admin perspective, because every one of those corporate users still has two accounts, their local one that is synched to On Premises AD, and the the external account shared from the new tenant as part of the MTO 2) From a user's perspective. For reasons that I cannot fathom (but this is coming direct from Microsoft after many attempts on my part to find a way) it seems that while you can control which licensed accounts appear on Teams search by controlling whether they are in the GAL and setting the appropriate switch in Teams Admin, all the unlicensed users appear whether you like it or not. The net result is that when someone on the old tenant starts typing in a name of someone in Corporate, they get two suggestions coming up. So the second question is, are those accounts actually necessary?
O365 SSPR require users to register when signing in
Hi Everyone Can someone please shed some light on this. In Azure SSPR under password reset>registration> require users to register when signing in Yes or No. Below is MS website explanation. Does that mean if I set it to Yes, if users go to office.com they are prompted to register in SSPR? What are the down side of choosing no, https://learn.microsoft.com/en-us/entra/identity/authentication/concept-sspr-howitworks#require-users-to-register-when-they-sign-in if they use modern authentication or web browser to sign in to any applications using Microsoft Entra ID. This workflow includes the following applications: Microsoft 365 Microsoft Entra admin center Access Panel Federated applications Custom applications using Microsoft Entra ID When you don't require registration, users aren't prompted during sign-in, but they can manually registerForce change password at next login on-premise and MS online
Hi Currently, I have a hybrid environment with AD on-premise, Azure AD sync (with password hash & SSPR), and Exchange Online. My goal is to force change the password at the next login from on-premise AD to MS online and vice versa. It's working. When I change the password on-premise AD, MS Online prompts me to change the password. It is not working when I set the account from the Admin center to force the password change at the next login; it does not sync to on-premise AD. The domain computer will not prompt to change password. Thanks in advance MS recommend to try this Install-Module -Name Microsoft.Graph Connect-MgGraph -Scopes "OnPremDirectorySynchronization.ReadWrite.All" Then run this command. $OnPremSync = Get-MgDirectoryOnPremiseSynchronization $OnPremSync.Features.UserForcePasswordChangeOnLogonEnabled = $true Update-MgDirectoryOnPremiseSynchronization -OnPremisesDirectorySynchronizationId $OnPremSync.Id -Features $OnPremSync.FeaturesSelf Service Reset password (SSPR)
Hi I have an odd situation with random users. When SSPR is enabled for them, they cannot login email on their iPhone corporate Intune device, is pushing the login to conditional access trusted locations blocked. Email works just fine with SSPR disabled. Anyone experience something similar.
Guidance Needed on Microsoft 365 Subscription for Teams App Development
I am currently developing an app for Teams and have set up accounts in the Azure portal, joined the developer program, and accessed the Teams developer portal. However, when attempting to log in to the Teams admin center, an error occurs: Internal calls to PLS Service have failed. We can't find the tenant region for tenantId. Please try again later to join the developer program, the message indicated: `Thank you for joining. You don't currently qualify for a Microsoft 365 Developer Program sandbox subscription.`. Research revealed that Microsoft discontinued the free subscription. A subscription is needed to access the Microsoft Teams admin center and for Teams app development. I can see various Microsoft 365 plans for businesses like Basic and Standard, as well as licenses available in the Microsoft 365 admin center. I am considering the Microsoft Teams Essentials license. However, there is confusion regarding whether to buy a subscription or a specific license, especially since active users in the 365 admin center are showing as unlicensed. Could anyone advise on which plan or license is necessary for Teams app development?Manage multiple tenants
Hi There, I have around 50 M365 customers to manage. Previously, in each tenant I create an unlicensed global admin account ( with .onmicrosoft.com account) which shared by our team. when customer need help, we will access it. understand that Microsoft will force all global admin to use MFA, but we have a challenge that each of the tenant will be access by multiple support from my team, if use MFA, it will affect our support efficiency. 2. yes, we do have a partner portal, we did use this way to access our customer's tenant, and, currently, Microsoft force to set expiry date for the GDAP, which we require to get consent from our customer to click the link. I just wonder how u guys manage or use which approach to support multiple tenants. Any idea?
Conditional Access Help
Hi - Thought this would be easy but it's not. We have a group of 5 temporary employees that need to access one custom built app in our environment. That app utilizes M365 authentication. I setup these users in a security group and want to block all access with the exclusion to this one app. The problem is, if I block Office 365, it does not allow them to login to the custom app. They get an error that blocks them, even though the app itself is excluded. I then exclude the app and Office 365 and it allows the login. This is frustrating because we cannot allow any access to Outlook, Sharepoint, OneDrive, etc. Any advice? When I try to search for just Exchange or Sharepoint by itself, there are no options to select under Cloud Apps.Usable Video Format for Microsoft Support?
I swear the ineptitude of Microsoft support knows no bounds. You give us the option to upload a video, but the format for which the WINDOWS OS's SNIPPET TOOL USES AS WELL AS CIipChamp that is referenced as a program to edit with FROM THE SNIPPING TOOL (which this forum WOULDN'T even allow me to have as a word here...) uses MP4 BUT MP4 IS NOT ALLOWED... I mean seriously who is in charge of this madness!? They should be ejected into the sun for this sort of stupidity, and then the tool tip gives you 0 information as well as the error. So freaking annoying and stupid.
