Office 365 - Changing Domain using Powershell

Hi,
I have about a hundred users on a domain ([email protected]) and I need to change to another domain ([email protected]) using Powershell.
May I know what commands are needed to accomplish this? I need to change the userPrincipalName, SIP and Primary SMTP to the new domain.
I have all the users in a CSV file.
Thanks!!

Hi Kindovic,
To bulk add user information from CSV file, please check the script below:
Bulk import the user information from CSV file
How to create users in bulk using csv file import
For the issue of office 365, I also recommend you to post this in Office 365 forum for more effective support:
Manage Office 365
Best Regards,
Anna

Similar Messages

Setting the shared templates location by Deploying Office 365 Midsized Business "using a network share" from a on-premise location

I found the question "Deploy Office 365 pro plus using a network share or from a on-premise locaiton" the most useful of the resources
on MS yet - but I am having difficulties getting the files to download for a local deployment.
The root of the issue, that I cannot find anywhere, is how do I set the shared templates location for users in the organization. First I thought a GPO, but I cannot find that setting in the GPO in MS.
Then I thought modifying the REG- but it is in a binary key which could include other information I may not want modified(Or does it matter?)
Then I looked for ways to download the deployment but launching from an elevated prompt as IT (Domain level) returns a useless error to paraphrase- 'sorry MSOffice didn't install- do you have enough disk space'.
I have downloaded the GPO objects, but not installed them, likely I will need those later though.
Just want to path all the users to a central repository of office/excel/access/outlook templates in addition to their local templates. Concise help in steps or sites that have solved the issue are Greatly appreciated : )

Hi,
you can use the GPO ADMX templates to configure the "Workgroup templates path".
This actually configures a registry setting named: "sharedtemplates".
The registry value/type/data is:
HKEY_CURRENT_USER\Software\Policies\Microsoft\office\15.0\common\general
Name: sharedtemplates
Type: REG_EXPAND_SZ (Expandable String Value)
Data: <UNC path to folder>
From the GPO reference workbook/sheet, for Office:
http://social.technet.microsoft.com/wiki/contents/articles/4976.selected-content-relating-to-group-policy-administrative-templates-adm-and-admx.aspx
Filename: office15.admx
Scope: User
Path: Microsoft Office 2013\Shared paths
Policy Setting Name: Workgroup templates path
Supported on: At least Windows Server 2008 R2 or Windows 7
Category: Shared paths
Explain Text: Specifies the location of workgroup templates.
Registry Key: HKCU\software\policies\microsoft\office\15.0\common\general!sharedtemplates
Note: it is supported to populate this setting, with a UNC path, but not with a web path.
e.g.: \\server01\shared\templates <this is valid>
e.g.: http://server01/shared/templates <this is not valid>
This constraint (for web URIs) can be difficult to work around. If you are using SharePoint, and think WebDAV might work, it doesn't seem to work for us :(
Of course, if you have SharePoint, there are much better ways to handle document templates, but, our users are familiar with this File -> New -> from template type of method...
It can also be set manually by a user:
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Create a Domain Controller and a Child Domain using Powershell

Is it possible to create a Domain Controller and a Child Domain using Powershell?

Yes, you can do that:
WS2008R2 -
http://technet.microsoft.com/en-us/library/cc731394%28v=ws.10%29.aspx
http://technet.microsoft.com/en-us/library/cc731873%28v=ws.10%29.aspx - This isn't technically PowerShell.
WS2012 -
http://technet.microsoft.com/en-us/library/jj574105.aspx
EDIT: You've asked this same question a few times now, is there something specific that's giving you trouble?
Don't retire TechNet! -
(Don't give up yet - 12,830+ strong and growing)

Office 365 email deployment using Outlook 2010 and PRF files

Hi,
I've been struggling to get Outlook 2010 setup with a new Office 365 deployment. I would like to use custom PRF files to get the new Outlook profiles configured. I have more than 100 users.
One of PRF files I'm using is shown at the end of this message. Each user will get a custom PRF file with his/her information already configured (mailbox, server name, etc...). I've obtained the corresponding Exchange server using:
Get-Mailbox <email> | select ExchangeGUID
I've attached the domain at the end of the GUID and then that's the Exchange server. It matches what you get with Outlook using Autodiscover.
Using these PRF fies I'm able to create a new default profile and set all the parameters as if I had create the profile manually. Two problems here though:
1) I don't know what to change in the PRF file to set the Logon Network Security to Anonymous Authentication under the Security tab (Exchange account properties)
2) When Outlook asks me for the username and password, it won't take it, and I know I'm using the right credentials. If I create the profile manually (not using Autodiscover) and I use the same configuration parameters in the PRF file, everything is ok. I have
already run all the updates and tools that come as part of Setup Desktop in Office 365. Actually I get the same results with Outlook 2013.
I'm looking for some help here or ideas how to roll Office 365 without having to go user by user and creating a new profile and waiting for Autodiscover to finish :)
PRF FILE for one of the users (i'm using [email protected] to avoid putting here the actual client's address):
;Automatically generated PRF file from the Microsoft Office Customization and Installation Wizard
; Section 1 - Profile Defaults
[General]
Custom=1
ProfileName=Office365
DefaultProfile=Yes
OverwriteProfile=Yes
ModifyDefaultProfileIfPresent=false
; Section 2 - Services in Profile
[Service List]
;ServiceX=Microsoft Outlook Client
ServiceEGS1=Exchange Global Section
Service1=Microsoft Exchange Server
; Section 3 - List of internet accounts
[Internet Account List]
; Section 4 - Default values for each service.
;[ServiceX]
;FormDirectoryPage=
;-- The URL of Exchange Web Services Form Directory page used to create Web forms.
;WebServicesLocation=
;-- The URL of Exchange Web Services page used to display unknown forms.
;ComposeWithWebServices=
;-- Set to true to use Exchange Web Services to compose forms.
;PromptWhenUsingWebServices=
;-- Set to true to use Exchange Web Services to display unknown forms.
;OpenWithWebServices=
;-- Set to true to prompt user before opening unknown forms when using Exchange Web Services.
[ServiceEGS1]
[email protected]
[email protected]
[email protected]
ConfigFlags=0x00000100
RPCoverHTTPflags=0x002f
RPCProxyServer=outlook.office365.com
RPCProxyPrincipalName=msstd:outlook.com
RPCProxyAuthScheme=0x0001
[Service1]
OverwriteExistingService=Yes
UniqueService=No
[email protected]
[email protected]
OfflineAddressBookPath=
OfflineFolderPathAndFilename=
; Section 5 - Values for each internet account.
; Section 6 - Mapping for profile properties
[Microsoft Exchange Server]
ServiceName=MSEMS
MDBGUID=5494A1C0297F101BA58708002B2A2517
MailboxName=PT_STRING8,0x6607
HomeServer=PT_STRING8,0x6608
OfflineAddressBookPath=PT_STRING8,0x660E
OfflineFolderPathAndFilename=PT_STRING8,0x6610
[Exchange Global Section]
SectionGUID=13dbb0c8aa05101a9bb000aa002fc45a
MailboxName=PT_STRING8,0x6607
HomeServer=PT_STRING8,0x6608
ConfigFlags=PT_LONG,0x6601
RPCoverHTTPflags=PT_LONG,0x6623
RPCProxyServer=PT_UNICODE,0x6622
RPCProxyPrincipalName=PT_UNICODE,0x6625
RPCProxyAuthScheme=PT_LONG,0x6627
AccountName=PT_UNICODE,0x6620
[Microsoft Mail]
ServiceName=MSFS
ServerPath=PT_STRING8,0x6600
Mailbox=PT_STRING8,0x6601
Password=PT_STRING8,0x67f0
RememberPassword=PT_BOOLEAN,0x6606
ConnectionType=PT_LONG,0x6603
UseSessionLog=PT_BOOLEAN,0x6604
SessionLogPath=PT_STRING8,0x6605
EnableUpload=PT_BOOLEAN,0x6620
EnableDownload=PT_BOOLEAN,0x6621
UploadMask=PT_LONG,0x6622
NetBiosNotification=PT_BOOLEAN,0x6623
NewMailPollInterval=PT_STRING8,0x6624
DisplayGalOnly=PT_BOOLEAN,0x6625
UseHeadersOnLAN=PT_BOOLEAN,0x6630
UseLocalAdressBookOnLAN=PT_BOOLEAN,0x6631
UseExternalToHelpDeliverOnLAN=PT_BOOLEAN,0x6632
UseHeadersOnRAS=PT_BOOLEAN,0x6640
UseLocalAdressBookOnRAS=PT_BOOLEAN,0x6641
UseExternalToHelpDeliverOnRAS=PT_BOOLEAN,0x6639
ConnectOnStartup=PT_BOOLEAN,0x6642
DisconnectAfterRetrieveHeaders=PT_BOOLEAN,0x6643
DisconnectAfterRetrieveMail=PT_BOOLEAN,0x6644
DisconnectOnExit=PT_BOOLEAN,0x6645
DefaultDialupConnectionName=PT_STRING8,0x6646
DialupRetryCount=PT_STRING8,0x6648
DialupRetryDelay=PT_STRING8,0x6649
[Personal Folders]
ServiceName=MSPST MS
Name=PT_STRING8,0x3001
PathAndFilenameToPersonalFolders=PT_STRING8,0x6700
RememberPassword=PT_BOOLEAN,0x6701
EncryptionType=PT_LONG,0x6702
Password=PT_STRING8,0x6703
[Unicode Personal Folders]
ServiceName=MSUPST MS
Name=PT_UNICODE,0x3001
PathAndFilenameToPersonalFolders=PT_STRING8,0x6700
RememberPassword=PT_BOOLEAN,0x6701
EncryptionType=PT_LONG,0x6702
Password=PT_STRING8,0x6703
[Outlook Address Book]
ServiceName=CONTAB
[LDAP Directory]
ServiceName=EMABLT
ServerName=PT_STRING8,0x6600
UserName=PT_STRING8,0x6602
UseSSL=PT_BOOLEAN,0x6613
UseSPA=PT_BOOLEAN,0x6615
EnableBrowsing=PT_BOOLEAN,0x6622
DisplayName=PT_STRING8,0x3001
ConnectionPort=PT_STRING8,0x6601
SearchTimeout=PT_STRING8,0x6607
MaxEntriesReturned=PT_STRING8,0x6608
SearchBase=PT_STRING8,0x6603
CheckNames=PT_STRING8,0x6624
DefaultSearch=PT_LONG,0x6623
[Microsoft Outlook Client]
SectionGUID=0a0d020000000000c000000000000046
FormDirectoryPage=PT_STRING8,0x0270
WebServicesLocation=PT_STRING8,0x0271
ComposeWithWebServices=PT_BOOLEAN,0x0272
PromptWhenUsingWebServices=PT_BOOLEAN,0x0273
OpenWithWebServices=PT_BOOLEAN,0x0274
CachedExchangeMode=PT_LONG,0x041f
CachedExchangeSlowDetect=PT_BOOLEAN,0x0420
[Personal Address Book]
ServiceName=MSPST AB
NameOfPAB=PT_STRING8,0x001e3001
PathAndFilename=PT_STRING8,0x001e6600
ShowNamesBy=PT_LONG,0x00036601
; Section 7 - Mapping for internet account properties. DO NOT MODIFY.
[I_Mail]
AccountType=POP3
;--- POP3 Account Settings ---
AccountName=PT_UNICODE,0x0002
DisplayName=PT_UNICODE,0x000B
EmailAddress=PT_UNICODE,0x000C
;--- POP3 Account Settings ---
POP3Server=PT_UNICODE,0x0100
POP3UserName=PT_UNICODE,0x0101
POP3UseSPA=PT_LONG,0x0108
Organization=PT_UNICODE,0x0107
ReplyEmailAddress=PT_UNICODE,0x0103
POP3Port=PT_LONG,0x0104
POP3UseSSL=PT_LONG,0x0105
; --- SMTP Account Settings ---
SMTPServer=PT_UNICODE,0x0200
SMTPUseAuth=PT_LONG,0x0203
SMTPAuthMethod=PT_LONG,0x0208
SMTPUserName=PT_UNICODE,0x0204
SMTPUseSPA=PT_LONG,0x0207
ConnectionType=PT_LONG,0x000F
ConnectionOID=PT_UNICODE,0x0010
SMTPPort=PT_LONG,0x0201
SMTPSecureConnection=PT_LONG,0x020A
ServerTimeOut=PT_LONG,0x0209
LeaveOnServer=PT_LONG,0x1000
[IMAP_I_Mail]
AccountType=IMAP
;--- IMAP Account Settings ---
AccountName=PT_UNICODE,0x0002
DisplayName=PT_UNICODE,0x000B
EmailAddress=PT_UNICODE,0x000C
;--- IMAP Account Settings ---
IMAPServer=PT_UNICODE,0x0100
IMAPUserName=PT_UNICODE,0x0101
IMAPUseSPA=PT_LONG,0x0108
Organization=PT_UNICODE,0x0107
ReplyEmailAddress=PT_UNICODE,0x0103
IMAPPort=PT_LONG,0x0104
IMAPUseSSL=PT_LONG,0x0105
; --- SMTP Account Settings ---
SMTPServer=PT_UNICODE,0x0200
SMTPUseAuth=PT_LONG,0x0203
SMTPAuthMethod=PT_LONG,0x0208
SMTPUserName=PT_UNICODE,0x0204
SMTPUseSPA=PT_LONG,0x0207
ConnectionType=PT_LONG,0x000F
ConnectionOID=PT_UNICODE,0x0010
SMTPPort=PT_LONG,0x0201
SMTPSecureConnection=PT_LONG,0x020A
ServerTimeOut=PT_LONG,0x0209
CheckNewImap=PT_LONG,0x1100
RootFolder=PT_UNICODE,0x1101
Account=PT_UNICODE,0x0002
HttpServer=PT_UNICODE,0x0100
UserName=PT_UNICODE,0x0101
Organization=PT_UNICODE,0x0107
UseSPA=PT_LONG,0x0108
TimeOut=PT_LONG,0x0209
Reply=PT_UNICODE,0x0103
EmailAddress=PT_UNICODE,0x000C
FullName=PT_UNICODE,0x000B
Connection Type=PT_LONG,0x000F
ConnectOID=PT_UNICODE,0x0010

Wow, even if we were to find out what to add to the PRF, it turns out each user mailbox has it's own unique server name (aka Virtual Connection Point). I cannot believe two departments of Microsoft aren't talking to each other!!!! ..... wait, that always
happens. 1 week later and probably 100 hours later I am just going to create a simple how-to for each user.
Here is the link I just found explaining the "virtual connection points". http://www.blackmanticore.com/2c209fbaa93ae6cf8f8dac5b50281f2e
I'm sure NEXT YEAR Microsoft will catch up with itself and add this option/feature in the Office Customization Tool to create PRF files that will actually work with their services.

Deleting Stale Office 365 online Mailboxes with Powershell

We are using Office 365 online for our student email system.
I want to remove any mailbox that hasn't been accessed in the last year.

Once you determine that, you can remove the mailboxes a number of ways - depending on how your onsite AD interacts with Office 365.
If you use DirSync, the users that have been deleted onsite should eventually be purged from Office 365, mailboxes included.
*To be honest, I have always deleted users manually using the method below, so I cannot affirm, from experience, that this is the case, so someone may correct me.*
You can manaully purge mailboxes as well (I had to do this a while ago) with PowerShell cmdlets.
$cred = get-credential
connect-msolservice -credential $cred
Remove-MsolUser –UserPrincipalName [email protected]
Yes, you have to install what is known as the Windows Azure Active Directory Module for PowerShell to use those commands (cmdlets).
http://technet.microsoft.com/en-us/library/jj151815.aspx
If that's not clear, please ask follow up questions.
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Connect Office 365 Exchange Online through Powershell

I am trying to perform some operations on Exchange online(Office 365) through powershell.
First I created a new powershell session and exported the modules to local as "o365", so that on any later operation I no need to use Import-PsSession to download the required modules
$cred = Get-Credential
$s = New-PSSession -ConfigurationName "Microsoft.Exchange" -ConnectionUri "https://ps.outlook.com/powershell/" -Credential $cred -Authentication Basic -AllowRedirection
Export-PsSession -session $s -outputModule o365
Now, I am creating new session and importing the existing module "o365".
$cred = Get-Credential
$s = New-PSSession -ConfigurationName "Microsoft.Exchange" -ConnectionUri "https://ps.outlook.com/powershell/" -Credential $cred -Authentication Basic -AllowRedirection
Import-Module o365
Get-DistributionGroup
While running the command "Get-DistributionGroup", powershell prompts me to enter the office 365 credentials once again. Is it possible to avoid entering the credentials once again? I don't want to use Import-PsSession, since it takes more time.

Hi,
Not sure, if the following cmdlets can make a difference. Anyway, suggest you to try these:
$UserCredential = Get-Credential
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection
Import-PSSession $SessionGet-DistributionGroup
Regards from ExchangeOnline.in|Windows Administrator Area | Skype:[email protected]

Deploy Office 365 Pro Plus using MDT 2013

Hello,
I'm currently evaluating O365 E3 and am specifically looking into what my options are for deploying Office 2013 Pro Plus when rolling out a new PC image. Currently I use MDT 2013 to deploy the image to new PCs and install Office 2010 along with other
applications. Can I use C2R with a config file pointing to a local repository of the installation files with MDT 2013?

Hi
This blog post by Rens will help you:
http://renshollanders.nl/2014/02/office-365-automatic-deployment-of-office-365-with-mdt/

Deploying Office 365 Pro Plus using System Center Configuration Manager 2012 SP1

Hello,
I am trying to deploy Office 365 Pro Plus to my client machines (more than 100) via. System Center Configuration Manager 2012 SP1. It will use one administrator account for installation. But as per the licensing, we can install Office for up to 5 PCs/Macs
and 5 more Windows tablets/iPads with one Office 365 Pro Plus licenses. If this is the case, then I cannot install Office 365 Pro Plus with one admin account to my 100+ machines, as it will violate the licenses of O365 Pro Plus.
So, what is the alternative approach?
Thanks
Raj

If this is the case, then I cannot install Office 365 Pro Plus with one admin account to my 100+ machines, as it will violate the licenses of O365 Pro Plus.
Hi,
this is incorrect.
There is no licensing restriction/control for the *installation* account at all, the licensing is related to who is *using* Office365ProPlus *after* installation is performed. This control, is implemented by the Microsoft Account, or OrgID, used to sign-in/activate
to Office365 when *using* Office365ProPlus.
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Office 365 Split domain question

Is it possible to run an on-premise Lync hosting 1 SIP domain, with on premise Exchange running a specific email domain say company1.com
Then have Office 365 host two other SIP and email domains. Company2.com and company3.com
I am trying to get my head around this configuration, or if it's even possible.

It's documented by TechNet:
http://technet.microsoft.com/en-us/library/jj205157.aspx
For outside documentation, a lot of what I'm seeing is outdated, so TechNet may be your best source for up to date information.
And the answer to the DNS question is, it depends. If you're Office365 only for those sip domains, and on premises only for the other sip domain, it doesn't necessarily even need to be a hybrid deployment. That said, if it is and users can
cross from on premises to off, the DNS records should point at the on premises deployment:
"When creating DNS SRV records for hybrid deployments, the records, _sipfederationtls._tcp.<domain> and _sip._tls.<domain>, should point to the on premises Access Proxy."
http://technet.microsoft.com/en-us/library/jj205403.aspx
Once they hit the on premises, they will be redirected to the online deployment if that's where their account is homed.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications

Fail to change "AddressState" using powershell cmdlet "Set-NetIPAddress"

PS C:\Users\webadm> Get-NetAdapter | Get-NetIPAddress IPAddress : 10.145.0.118 InterfaceIndex : 12 InterfaceAlias : Ethernet AddressFamily : IPv4 Type : Unicast PrefixLength : 24 PrefixOrigin : Manual SuffixOrigin : Manual AddressState : Deprecated ValidLifetime
: Infinite ([TimeSpan]::MaxValue) PreferredLifetime : 00:00:00 SkipAsSource : False PolicyStore : ActiveStore PS
C:\Users\webadm> Get-NetAdapter | set-NetIPAddress -IPAddress 10.145.0.118 -AddressFamily IPv4 -AddressState Preferred set-NetIPAddress : No matching MSFT_NetIPAddress objects found by CIM query for instances of the ROOT/StandardCimv2/MSFT_NetIPAddress
class on the CIM server: SELECT * FROM MSFT_NetIPAddress WHERE ((IPAddress LIKE '10.145.0.118')) AND ((InterfaceIndex = 12)) AND ((InterfaceAlias LIKE 'Ethernet')) AND ((AddressFamily = 2)) AND ((AddressState = 4)). Verify query parameters and retry. At line:1
char:18 + Get-NetAdapter | set-NetIPAddress -IPAddress 10.145.0.118 -AddressFamily IPv4 -A ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : ObjectNotFound: (MSFT_NetIPAddress:String) [Set-NetIPAddress],
CimJobException + FullyQualifiedErrorId : CmdletizationQuery_NotFound,Set-NetIPAddress
Can anyone tell what's going wrong? thanks.

Hello !
To add an IP address, you have to use New-NetIPAddress cmdlet.
Example:
New-NetIPAddress -InterfaceIndex 12 -IPv4Address 10.145.0.118 -PrefixLength 24
If you have to remove the
10.145.0.118 address, you can use Remove-NetIPAddress.
Hope this helps.
Note: This posting is provided 'AS IS' with no warranties or guarantees, and confers no rights. Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable. This helps the community, keeps the forums tidy, and
recognises useful contributions.

SP 2013 Client Object Model: What credentials to use for Office 365 and sites behind ADFS 3.0?

I'm using the SharePoint 2013 Client Object Model to access a site that is either in Office 365 or behind an ADFS 3.0 login screen, is it sufficient to use the new SharePointOnlineCredentials credentials
or do I need other types of credentials for the sites behind ADFS 3.0 ? Is so, what type of credentials would I use for the sites behind ADFS 3.0?
using (ClientContext ctx = new ClientContext(siteUrl))
ctx.Credentials = new SharePointOnlineCredentials("some user", "a secure string password");
while (ctx.HasPendingRequest)
ctx.ExecuteQuery();
// etc.

Hi,
According to your post, my understanding is that you want to know the ways to get credential either in Office 365 or sites behind ADFS 3.0.
For Office 365, you can use SharePointOnlineCredentials Object to get credential. For SharePoint sites behind ADFS 3.0, you can use NetworkCredential Object:
ctx.Credentials = new NetworkCredential(UserName, Password, Domain);
The link below will provide more information about using the ADFS FedAuth Token programmatically through the SharePoint Client Object Model:
http://samirvaidya.blogspot.com/2013/05/using-adfs-fedauth-token.html
Best regards
Patrick Liang
TechNet Community Support

Disable site sharing in Office 365 using CSOM

I have a requirement to disable sharing of sites and documents in Office 365 site collection using CSOM.
Manually from UI, I can disable sharing by unchecking Access Request Settings under Site Settings.
But could not find a way to do it using CSOM.

Hi,
If it is an on premises environment, there is a property “RequestAccessEnabled” in SPWeb class in SharePoint Object Model can be used to change the
setting:
https://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spweb.requestaccessenabled.aspx
However, in an online environment, the SharePoint Object Model is not an option, what’s more, in Client Object Model which is designed for client side use, there is
no such a property in Web class available:
https://msdn.microsoft.com/en-us/library/microsoft.sharepoint.client.web_members.aspx
It means that it is not able to change the “Access Request Settings” with the client side technology such as JavaScript.
Thus, I would suggest you submit a feedback to the Office Developer Platform if there any expectation about the future version of Office 365:
http://officespdev.uservoice.com/
It
is a place for customers provide feedback about Microsoft Office products. What’s more, if a feedback is high voted there by other customers, it will be promising that Microsoft
Product Team will take it into consideration when designing the next version in the future.
Best regards
Patrick Liang
TechNet Community Support

Using different Office 365 Account on Windows 8.1 with Microsoft Account

Onedrive does not have any connection to Office 365. They are completely independent of one another.
Office 365 has no use of Microsoft Accounts (other than when sharing with people who are not in your tenant)

I have a customer that has boughta new team member a laptop with Windows 8.1 on it.The customer uses a shared One Drive Account across all of the teams machines to share data between them.All the other machines are using windows 7 professional with the One Drive desktop app installed, allowing them to do that. On the windows 8.1 laptop though, they are forced to sign into the laptop with a the Microsoft account to access OneDrive on that machine, due to it being integrated with the OS. This however, has caused issues because the team member then has access to everything under that Microsoft account and not just access to the one drive which is all the other team members have access to. I haven't found a way around that but if you happen to know one, please let me know.Anyway, now the customer wants to add office 365 to the laptop using...
This topic first appeared in the Spiceworks Community

Autodiscover not working correctly when Office 365 integrated with Server Essentials 2012 R2

Hello!
This last weekend I setup our server as new and to ease the creation of users, integrated with our Office 365 (which to this point has worked fine) and imported the users. This had a somewhat unexpected side effect in that the import used the email address
as for the user forename and then synced that change back to Office 365 and so needed to enter this information back in on the dashboard which synced back to Office 365. This may or may not have any relevance to our issue below.
I should also point out that we have our own domain name so within the original Office 365 setup we had just one .onmicrosoft.com user with all the rest setup with our own domain name.
At the weekend when it came to the client install, Outlook (2010 or 2013) would fail on the autodiscover with it asking again for credentials but critically displaying a server name of .contoso.com rather than the office365srvr.contoso.com . As I mention,
Office 365 had been operating fine for some time and DNS records where checked and have been set for sometime. I spoke to Office 365 support and after a while come up with a temporary solution (so that I could complete the client installs) of assigning each
user a onmicrosoft address, using that in the new account wizard to pick up the server correctly and then signing in the the Office 365 .contoso.com credentials.
This worked OK to get us past the weekend (although I am having to reset up profiles on quite number of users where they get disconnected but with no credentials box appearing) but isn't a solution. The clients do not see public folders or their archives
and of course we don't want to keep having to reset the profiles.
I'm think that there must be something in the internal network that needs reconfiguring but I don't know what. I have tried pointing the client to an external DNS server just in case the internal DNS server was throwing the autodiscover out but this has
made no difference.

Ah - solved my own problem.
Despite the domain DNS record looking OK and the Office 365 Portal domain checker not highlighting any issue, it looks as though the autodiscover is picking up an imap account provided by the web host.
I've added an alias on the local DNS server to point to the Office 365 autodiscover server and this has solved the problem.

Cmdlts for changing password in powershell.

I am trying to change a users Office 365 email password in powershell. Everything I read is telling me to use Set-MsolUserPassword cmdlet, however that reports back as not being a valid cmdlet. I have tried this in Powershell and Powershell ISE with
the same results. Running Windows 8.1

You need to download and install the WAAD module for PowerShell first:
http://msdn.microsoft.com/en-us/library/azure/jj151815.aspx

Office 365 - Changing Domain using Powershell

Similar Messages

Maybe you are looking for