Forum Discussion

a2hawks's avatar
a2hawks
Copper Contributor
Feb 10, 2024

Take Over of Unmanaged Directory and Teams Question

I am kind of in a unique situation. Customer has been using their company email for MS services for almost 2 decades, mostly for Skype.

 

I have figured I can get them to remove their business email from Skype and they can use a phone number and change the email to another one temporarily (at least). Could not find anything definitive on this, just guessing......

 

They have been invited as guests to Teams Channels hosted by other companies.

 

My question is: When I do a take over will they be required to have a teams license to participate in those channels.

 

I am hoping they won't need to be licensed for now.

 

I am 6 months minimum from getting procurement, and do not want to screw up what they are using, I just need to get in to VLSC (which now requires a verified Entra ID). They have onsite exchange.

 

From previous experience, I know that when you have to license for teams, it creates an exchange email address whether you want it or not, and anytime I have done this, it creates delivery issues with other exchange online accounts. So I don't want to mess with licensing M365 until I an ready to migrate online.


  • Here's a breakdown of your situation and potential solutions:

    Current Situation:

    Customer has been using their company email for Microsoft services (mainly Skype) for 20 years.
    They are currently unmanaged and want to move to a Microsoft Volume Licensing Service Center (VLSC) subscription.
    They participate in Teams channels as guests from other organizations.
    Challenges:

    Removing the business email from Skype might require additional verification or support from Microsoft.
    Switching to a temporary email might not be a long-term solution.
    Participating in Teams channels as guests might require a Teams license in the future.
    Solutions:

    1. Taking Over the Unmanaged Directory:

    Contact Microsoft Support: Explain your situation and seek guidance on removing the business email from Skype and transitioning to a new email address. They can provide the most accurate and up-to-date information.
    Consider Alternative Solutions: Explore alternative communication methods within Microsoft services that don't require a business email address, such as phone numbers or personal accounts (if appropriate).
    2. Teams Guest Participation:

    Guest access limitations: Currently, guest users in Teams can participate in chats, calls, and meetings without requiring a license. However, Microsoft might introduce licensing requirements for guest access in the future.
    Monitor Microsoft Updates: Stay informed about any changes to guest access policies in Teams to ensure you're prepared for potential licensing needs.
    3. Avoiding Unwanted Exchange Mailboxes:

    Licensing options: Consider M365 Business Basic, which doesn't automatically create Exchange mailboxes. This option allows access to Teams without email functionality.
    Careful planning: If migrating to Exchange Online is necessary in the future, plan the migration carefully to avoid delivery issues with other accounts.
    Additional Recommendations:

    Communicate with the customer: Explain the potential challenges and limitations associated with their current setup and proposed solutions.
    Develop a migration plan: Create a roadmap for migrating to a managed environment and online services, considering licensing requirements and potential email delivery issues.
    Seek professional help: If needed, consult with a Microsoft partner or IT professional to assist with the transition and ensure smooth operation.
    Remember, it's crucial to prioritize data security and user experience while navigating this situation. Carefully consider all options and potential consequences before implementing any changes.
    • a2hawks's avatar
      a2hawks
      Copper Contributor
      They already have a VLSC for products they have had for years. MS just now requires that you take over the domain to create an azure account to access the VLSC.

      The problem I have is that it is not totally clear what will happen after I take control with the account.

      And contacting MS support is a crapshoot about which of the 48 departments I should contact, and then I need to get someone who can actually supply this information. I tried that a few years ago and got the phone equivalent of a shoulder shrug.

      I have done everything you suggested with the customer, this is not necessarily my first rodeo in the 30 years I have been in this business. Matter of fact, the cloud has really been a problem in that there is not real ability for a test environment to find out what the pitfalls are like you could with on prem (Unless you have pockets deep enough to be able to afford a cloud test environment).

      Actually your O365 basic suggestion is of no use, as if a user logs in with their business account, it will bounce them because they do not have a teams license, and a teams license requires an exchange account. I know this because I have run into this issue with another customer.
      • smylbugti222gmailcom's avatar
        smylbugti222gmailcom
        Iron Contributor

        a2hawks 

        I understand your concerns about taking over the domain for accessing the VLSC and the lack of clarity about the potential consequences. It's frustrating to navigate complex procedures with limited information and unhelpful support experiences.

        Here's what I can offer to help:

        1. Clarify the Potential Impact:

        While I can't definitively predict the exact outcome, I can provide some general insights based on Microsoft's practices:

        • Taking control of the domain shouldn't directly affect existing VLSC access or product licenses. Microsoft aims to simplify access management and ensure secure authentication.
        • You might need to create new Azure AD accounts for users who need to manage VLSC access. This could involve assigning appropriate roles and permissions within the Azure AD tenant.
        • There might be some initial configuration or migration steps involved. Microsoft typically provides guidance and resources for these processes.

        2. Recommendations:

        • Contact Microsoft support again, but this time, try a different approach:
          • Explain your specific concerns and questions clearly. Mention the lack of clarity you've encountered and request detailed information about the potential impact on your existing VLSC access and product licenses.
          • Be persistent and ask for clarification if necessary. Don't settle for vague answers.
          • Consider contacting a Microsoft partner or consultant specializing in Azure AD and VLSC management. They might have deeper knowledge and experience navigating these processes.

        3. Alternative Solutions:

        • Explore alternative methods for accessing the VLSC:
          • Check if there are any existing Azure AD accounts associated with the domain that can be used for VLSC access.
          • Consider using a third-party solution for managing your Microsoft licenses, which might offer more flexibility and control.

        4. Remember, taking control of the domain is usually a necessary step for managing Azure AD and other Microsoft services associated with your organization. However, it's crucial to understand the potential implications and proceed with caution.

        Regarding your O365 basic suggestion:

        You're right that a user with a business account without a Teams license won't be able to access Teams. However, this is a separate issue from accessing the VLSC. It's important to differentiate between these two functionalities and address them independently.

        I hope this information helps you navigate this situation better.

    • a2hawks's avatar
      a2hawks
      Copper Contributor

      Kidd_Ip 

       

      Eventually, the idea is to migrate to exchange online, and begin using Teams in place of Skype. They will be using the office apps as well.

       

      My chief concern at the moment would be taking over the unmanaged directory without causing issues with the way they currently use teams. Currently this means they participate as guests in several teams channels that belong to their partner companies.

       

      BTW this whole thing started just to get access to the VLSC for downloads and serial keys.

Resources