MCA billing account stuck in "under review" status for 4+ days, no resolution
I'm the Global Admin for a Microsoft 365 tenant (domain: fortunamg.net) recently transitioned from a GoDaddy CSP reseller relationship to a direct Microsoft Customer Agreement (MCA) billing account. After setting up the MCA billing account and adding a payment method, I attempted to make an edit to my billing account address (updating to the new 9-digit zip code format). This triggered an "Account under review" status, which states the review usually takes up to 2 days. It has now been over 4 days with no update or email notification. This review is blocking me from purchasing a subscription, which I need to do to restore an active Microsoft 365 subscription on this tenant (currently showing as "Disabled" following the GoDaddy detach). Billing Account ID: 7793dd6e-68c9-5362-c5e2-3fe091b9854c Domain: fortunamg.net Could someone help check the status of this review or escalate to the appropriate team? Phone support has been unable to resolve this. Thank you.Extend M365 Archive Quota capacity
In my organization, we are currently on the O365 E5 License with default 100GB mailbox size per user and 1.5TB archive quota. However, due to organizational policy and regulatory requirements, we are expected to keep all the data from inception. Hence, the requirement for a solution to extend our archive size from 1.5TB. From the official Microsoft documentation, https://learn.microsoft.com/en-us/office365/servicedescriptions/exchange-online-archiving-service-description/exchange-online-archiving-service-description#archive-storage-quota the maximum expansion of the archive mailbox is 1.5TB. Is it possible to extend the archive storage to an Azure blob? Like an automated script that moves the data from the Archive mailbox for each user to the Azure blob or any other storage service that does not have storage size limitation. I am open to suggestions. ThanksInterface Views in Microsoft 365 Admin Center
1. Simplified View Purpose: Designed for small businesses or organizations with limited IT resources. Features: Streamlined dashboard with essential tasks like user management, license assignment, and password resets. Minimal configuration options to reduce complexity. Quick access to support and basic service health info. Use Case: Ideal for admins who need to perform routine tasks without diving into advanced settings. 2. Dashboard View (Advanced View) Purpose: Tailored for medium to large enterprises with complex IT environments. Features: Full access to all admin centers (Exchange, SharePoint, Teams, etc.). Advanced analytics, reporting, and configuration tools. Role-based access control and security management. Customizable widgets and navigation for personalized workflows. Use Case: Suitable for IT teams managing multiple services, users, and compliance requirements. Customization Needs Are there specific tasks we perform frequently that can be automated in the dashboard?
Administrative Units - are they a possible solution in this case?
Hi, I'm looking at a situation where a company has two divisions, which we will call Corporate and Operations. They are geographically distinct as well as having significantly different requirements in terms of security, data access, mobile device control, applications requirements and other factors. At the current time, for mostly historical reasons, all IT is run from Operations, primarily based on a Microsoft 365 Tenancy. This isn't working well, and for a variety of reasons it seems it would be significantly preferable if the current Admins dealt with, and could only access, things related to Operations while new admins deal with Corporate. If any admin is going to have access to everything it needs to be Corporate (e.g. Operations admins should not be able to see Corporate emails, the reverse is less of an issue) A solution they are seriously considering is simply starting a new Microsoft 365 Tenancy for Corporate and then linking between them as required, possibly using a Multi Tenant Organization. The divisions appear to be distinct enough this could function quite well. They own several domains and apparently, email addresses are currently split divisionally to two of those domains. However, I have just come across Administrative units and wonder if an alternative might be to use those? I'm still on the learning curve for 365 so despite having a look at the documentation it's currently unclear to me what the powers and restrictions that can be assigned to the administrator of a given unit.
Migrating to 365 with 2 domains
I have a client that has two different domains (old and new). Example: Old email: mailto:email address removed for privacy reasons new email mailto:email address removed for privacy reasons. It looks like their provider created alias's for the new domain. Problem is they still get email going to the old email that get's forwarded(?) to the new email. I want to migrate over to 365. I'm pretty sure the migration will work to transfer over their email history using the new email, but I'm not sure how the forwarding will work. Can I create alias's for the old email in 365 to do the same?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.
IMAP email migration
I'm in the middle of migrating mailboxes from an IMAP server to 365. On the IMAP end, I have a user who has 2 email accounts with 2 (large) mailboxes and wants them merged into one Exchange user mailbox / account. Is this possible via standard migration tool ? I've migrated the first IMAP mailbox in one CSV file, but when I created a second CSV for the other I not unsurprisingly got the error: "Error: UserDuplicateInOtherBatchException: The user 'blah' is already included in migration batch 'blah' Please remove the user from any other batch and try again." I'm hoping to try and avoid a manual export/import of the second IMAP account if I can help it...
Office 365 rollout
Order of 365 rollout. I have jus moved to another company and they are rolling out office 365. They are moving over everyone to Teams and OneDrive and later they are migrating Exchange. I think there is a problem with migrating Exchange after Teams and it has to do with AD profiles, but I am not sure. Can someone please give me best practice on this and can it be done in this order? Thanks Warren